Repository navigation
[CI] Gate SCL publication on dependency audits - #197
Draft
lucaspimentel wants to merge 3 commits into
Draft
lucaspimentel wants to merge 3 commits into
lucaspimentel wants to merge 3 commits into
Conversation
This branch has not been deployed
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.
What does this PR do?
--lockedfor all release builds.Motivation
Establish strict publication-time enforcement before considering changes to merge-time enforcement. Findings, installation/refresh failures, timeouts and incomplete index checks must block publication, including on retries or with inherited warm caches.
Additional Notes
Describe how to test/QA your changes
test_mini_agent_tcp_handles_requestsexplicitly excluded for the known port-8126 collision. Doctests pass with existing ignores unchanged.$HOMEin the shared builder.This remains a draft: complete the build matrix and non-publishing release-job integration validation before marking ready. Local sentinel tests exercise failure/retry blocking, but do not prove deployed publication wiring. No production publication, signing, release upload or registry push was used for testing.
Reproduction commands and fixture provenance: test README.