Repository navigation
fix(*): apply approved expiring publishing audit exceptions - #34
Merged
Merged
Conversation
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.
Scope
publish-packages.yml; use the same native inline audit logic and fixed expiry as CI.Exact exceptions and expiry
Both exceptions expire at 2026-10-22 05:37:00 UTC, with no extension:
braces@3.0.3. The merged CLI glob size/depth guards mitigate the reviewed input path; tooling consumers remain affected.http-cache-semantics@4.2.0through the reviewed rootlerna@9.0.7dependency paths. Reviewed callers use private caches on fresh runners; this does not authorize shared-cache usage.Every other advisory remains blocking regardless of severity. Registry errors, unexpected statuses, invalid reports, muted findings, missing dependency paths, and inconsistent counts fail closed. At expiry, either remaining advisory blocks again; a clean report still passes. Accepted risks remain visible in warnings and the job summary. Remove the exceptions when patches are available; no security alert is dismissed.
Preserved release safeguards
next, thereleaseenvironment approval, and exact approved-commit verification remain unchanged.betadist-tag remain unchanged.Validation
The separately approved Codecov allowlist correction is applied directly in repository settings, adding only its exact
actions/github-scriptdependency. Coverage rerun is green.Nothing has been merged, tagged, or published by this work. No release workflow has been dispatched.