Repository navigation
馃悰 fix(release): enforce lock and cutoff gates - #4
Merged
Merged
Conversation
Reject unbounded Nab cutoff overrides and project-level policy bypasses. Keep test-only tools outside the committed release lock. Test the Windows install and lock refresh paths against their failure modes.
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.
Enforce the seven-day Nab cutoff for package and index settings, and reject project
nab.tomloverrides that the policy checker cannot inspect. Reviewed package exceptions now permit only bounded upload timestamps. The lock refresh and release asset paths fail when a required API read fails.The committed
pylock.tomlcontains release tools only. Action tests resolve test-only packages afresh into a temporary lock and serve a local index; hash-checked release-tool downloads and fresh test dependency resolution still use PyPI. The Windows-shaped environment and stale-lock tests exercise the failures they guard against.