chore(deps): enforce lockfile release age with uv - #263
Merged
Conversation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe dependency configuration adds a three-day ChangesDependency policy
Estimated code review effort: 1 (Trivial) | ~5 minutes 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
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.
Summary
Move the 3-day lockfile release-age enforcement to the layer that can actually evaluate transitive package upload times.
minimumReleaseAge: "3 days"policy unchanged for direct dependency updates.pep621lockFileMaintenanceupdates from Renovate's unsupportedminimumReleaseAgecheck.exclude-newer = "3 days"to[tool.uv]so uv enforces the same cooldown during lockfile resolution.uv.lockwith the repository-pinned uv0.12.1using plainuv lock(no--upgrade).Lockfile result
The lockfile regeneration changed metadata only; no dependency versions or artifact hashes changed:
Validation performed before opening this PR
uv lockcompleted successfully with the project-pinned uv0.12.1on a GitHub-hosted runner.renovate-config-validator --strict renovate.jsoncompleted successfully.renovate.json,pyproject.toml, anduv.lock.Scope
This is a tooling-only change. It does not modify integration runtime, migration, workflows, documentation, versions, or the pytest / PHACC / Home Assistant compatibility policy. The separate compatibility failures in Renovate PRs #258 and #259 are intentionally out of scope.
Summary by CodeRabbit