[chores] Add label guardrails in release process#2063
Merged
Conversation
Drarig29
commented
Jan 19, 2026
Comment on lines
+224
to
+232
| echo | ||
| echo -e "${RED}${BOLD}⚠️ You are not done!${NC} Please setup OIDC on each package at the links below." | ||
| echo | ||
|
|
||
| for pkg in "${missing_packages[@]}"; do | ||
| echo -e " - Opening ${BLUE}https://www.npmjs.com/package/$pkg/access${NC}" | ||
| open "https://www.npmjs.com/package/$pkg/access" | ||
| done | ||
| echo No newline at end of file |
GabrielAnca
reviewed
Jan 20, 2026
GabrielAnca
approved these changes
Jan 20, 2026
This was referenced Jan 20, 2026
Merged
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
2 participants
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 and why?
This PR changes the job order during the release process to have quick access to the draft release.
After the draft release is created,
pre-approval-checksand allbuild-*jobs run in parallel, and are required before startingnpm-publish.And the
pre-approval-checksjob can add aoidc-setup-required ⚠️label, which needs to be cleared with aoidc-setup-done ✅label. Addingoidc-setup-done ✅is now part of the first-time publishing process.How?
pre-approval-checksjob after thecreate-draft-releasejobpre-approval-checksas a direct requirement fornpm-publishReview checklist
Tested with
GITHUB_TOKEN=$(gh auth token) GITHUB_SHA=04b0d1cc47ab5f3ad479d0603df5acc1c6e01ba0 bin/check-npm-packages.shon #2062