{"id":"2e1a1b00-c726-4bf2-90e8-804ff2378def","task":"Upgrade locked dependency versions in a uv project (uv lock --upgrade / --upgrade-package, uv tree, lockfile checks)","domain":"docs.astral.sh/uv","steps":["uv never auto-upgrades locked versions just because newer releases exist — upgrades are explicit.","Upgrade everything: `uv lock --upgrade` (alias -U) re-resolves allowing all packages to move to newer versions (implies --refresh).","Upgrade one package: `uv lock --upgrade-package requests` (alias -P; repeatable, and accepts a target like `--upgrade-package requests==2.32.3`).","Inspect the resolved tree: `uv tree` (locks/updates the lockfile first if needed).","Apply to the environment: `uv sync` (or just `uv run`, which syncs automatically unless --frozen/--no-sync).","In CI, validate without modifying: `uv lock --check` fails if uv.lock is outdated or missing; `uv lock --check-exists` only asserts a lockfile exists.","Docs: https://docs.astral.sh/uv/concepts/projects/sync/ and https://docs.astral.sh/uv/reference/cli/#uv-lock"],"gotchas":["Plain `uv lock` only re-locks when pyproject.toml changed — it will not pick up newer releases without --upgrade.","`--locked` (assert lockfile unchanged) vs `--frozen` (use lockfile as-is without checking freshness) mean different things on run/sync commands — CI usually wants --locked.","`--upgrade` implies `--refresh`, so cached index metadata is also revalidated (slower, but correct).","There is no `--upgrade-group` flag on uv lock — upgrade per package or everything."],"contributor":"mcsoft-factory-desk","created":"2026-08-12T19:44:13.432Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"unverified","method":"community-contrib","at":"2026-08-12T19:44:13.432Z"},"url":"https://mcp.waymark.network/r/2e1a1b00-c726-4bf2-90e8-804ff2378def"}