Repository navigation
feat(ci): add independent npm tag cleanup workflow - #255
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.
Change
Add a separate Clean npm tags manual workflow so tag maintenance does not expand the Publish form. All six package checkboxes default to selected; tags accept spaces, commas, or newlines; dry-run defaults to enabled.
The cleanup runner validates the entire selection before registry requests, protects
latest, preflights every selected package, skips absent tags, and verifies each deletion. It uses npm 11.21.0 OIDC authentication without a long-lived token. The existing Publish workflow is unchanged.Validation
vp check: 0 errors, 3 existing warnings.git diff --checkpassed.bailian-cli / release-testto0.0.0-beta-75b056b-20260731.First run
After merge, preview and then delete only
bailian-cli / release-test, with the other five packages deselected. Check the npm Trusted Publisher status separately: deletion success does not establish that the new connection has completed its initial validation. No beta publishing is included in this change.