chore: pin deps so Renovate honors minimumReleaseAge (reliable automerge)#820
Merged
Conversation
ShapePipe had no repo Renovate config — everything came from Mend defaults. Two knobs, layered on top of those defaults, to make dependency automerge hands-off: - rangeStrategy = update-lockfile: pyproject.toml carries floor constraints (major-version signals); uv.lock is the real pin. Bump the lock for minor/patch updates, never rewrite the floors. (Non-lock ecosystems — Dockerfile, github-actions — fall back to "replace" automatically.) - minimumReleaseAge = 0 days: removes the release-age gate that was stalling automerge. With floor ranges, Renovate targets an aged version but `uv lock` resolves the floor to the newest in-range release — which may still be inside the age window — and Renovate can't pin uv to an exact version (renovatebot/renovate#41624), so the artifact update fails (this blocked #816). CI (full test suite + example pipeline, every PR) is the real safety gate for a dependency bump, so gate on CI, not a waiting period. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CBC6HKdgXaZ7ei5XfdvZGo
…lay) Keep the release-age gate — the point of it is supply-chain defense: a hijacked-but-legitimate package (compromised maintainer / malicious release) gets a detection window before it auto-merges — and make automerge reliable at the same time. Root problem: with floor ranges (>=) + rangeStrategy=update-lockfile, `uv lock` resolves the floor to the newest in-range release, which may be too fresh, and Renovate can't pin uv to an exact aged version (renovatebot/renovate#41624). So it fails the artifact update instead of waiting — this is what stalled #816. Fix: rangeStrategy=pin writes the exact aged version into pyproject.toml, so uv can't overshoot and minimumReleaseAge is honored. internalChecksFilter=strict ensures Renovate only ever acts on versions past the age gate. minimumReleaseAge set explicitly (3 days) so the control is owned in git, tunable. shapepipe ships as a container and isn't on PyPI (an app, not a library with downstream installers), so pinning is the appropriate, standard choice; the abstract-floors design targets libraries. Gates DIRECT deps only — transitive deps in uv.lock still float via lockFileMaintenance. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CBC6HKdgXaZ7ei5XfdvZGo
cailmdaley
changed the title
cailmdaley
added a commit
that referenced
this pull request
Jul 13, 2026
Match the docs to the strategy landed in #820: shapepipe pins deps to exact versions in pyproject.toml so Renovate can honor a supply-chain release-age delay (it can't hold uv back to an aged version through a floor range — renovatebot/renovate#41624). shapepipe ships as a container, not a published library, so there are no downstream installers that abstract floors would serve. Updates CLAUDE.md and the pyproject.toml header, which both still described the old abstract-minimums convention. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CBC6HKdgXaZ7ei5XfdvZGo
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
ShapePipe has no repo Renovate config — everything comes from Mend defaults, and dependency automerge is unreliable: grouped update PRs (#816) stall on a
renovate/artifacts"Artifact file update failure."The failure is a supply-chain-gate mechanics problem, not a real conflict.
pyproject.tomluses floor constraints (tqdm>=4.68.1). Renovate wants to move to an aged version (tqdm 4.68.3, past the minimum-release-age window), but updates the lock viauv lock, which resolves the floor to the newest in-range release (4.68.4) — still too fresh. Renovate can't tell uv to pin an exact version (renovatebot/renovate#41624), so it fails instead of waiting.Keep the release-age gate — it's the point
minimumReleaseAgeis a supply-chain defense: a hijacked-but-legitimate package (compromised maintainer, malicious release — the common attack now) gets a detection window before it auto-merges into the pipeline. We want to keep it, not drop it. The task is making Renovate actually honor it.The fix
A
renovate.jsonlayered over the Mend defaults:rangeStrategy: "pin"— the one way Renovate can honorminimumReleaseAgewith uv. It writes the exact aged version intopyproject.toml, souv lockcan't overshoot to a too-fresh release. Renovate's own recommendation for applications.internalChecksFilter: "strict"— only ever act on versions that have passed the age gate.minimumReleaseAge: "3 days"— the supply-chain delay, now owned in git (not an invisible Mend toggle) and tunable. Bump it for a longer detection window.Trade-offs to weigh (your + Martin's call)
==pins. This departs from the CLAUDE.md "abstract floors / uv.lock is the pin" design. But that design's rationale is downstream flexibility for library installers — and shapepipe isn't a library: it's not on PyPI, it ships as a container built fromuv.lock. For an application, pinning is the standard, secure choice. Renovate will open a one-time "Pin dependencies" PR to do the rewrite.minimumReleaseAgegates the deps Renovate sees (direct, in pyproject). Transitive deps inuv.lockstill float to latest vialockFileMaintenance— an existing gap, not made worse here.ngmix,cs_utilvia[tool.uv.sources]) — pinning should leave their git refs alone, but worth a glance on the first run.If you'd rather keep abstract floors and accept that automerge needs an occasional nudge (the failures self-heal as versions age), say so and I'll pare this back to just documenting that.
Note
Config takes effect once merged to
developand Renovate re-runs; a malformed config surfaces as a Renovate comment, not a CI failure here. Validated as well-formed JSON against the schema.🤖 Generated with Claude Code