Repository navigation
fix: verify main CodeQL analysis before package releases - #4
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.
Summary
Publication was blocked because the guard required the PR-only CodeQL security check on main. Require the successful official CI/analysis jobs, then verify the exact main commit's completed CodeQL analysis and no open CodeQL alerts through the read-only API. Continue to reject unsuccessful security-app checks when present.
Adds only
security-events: readto publication/Release jobs. Package source and 0.0.1 manifests are unchanged. No security gate is bypassed.Validation
pnpm qualitypasses, including coverage, installed tarballs, workflow/security guards, public scan and dependency audit.Release status
No package has been published yet. Merge after green checks as part of the authorized 0.0.1 release, then publish through the guarded workflows.