Repository navigation
ci: separate npm OIDC publishing from changepacks - #11
Merged
Merged
Conversation
owjs3901
marked this pull request as ready for review
September 10, 2026 10:21
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
1 participant
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.
The npm OIDC configuration was rolled back when changepacks checked out the earlier release source, so its built-in dry-run invoked Bun and failed before npm authentication.
Follow the working csstype-extra publication pattern: run checks, let changepacks select package targets with
publish: false, then build and publish from a fresh workflow checkout usingnpm publish --access public --ignore-scripts. Keeppublish.ymlunchanged as the trusted-publisher filename, retain Node 24/npm >=11.5.1 and job-scoped OIDC permission, and remove unused custom changepacks publish commands.A separate finalization job runs only after npm succeeds and handles the existing 1.0.4 draft release. This workflow does not depend on changepacks/action#8.
Validation:
Recovery: if npm fails, use Re-run failed jobs to preserve changepacks target outputs. With the reference workflow's
publish: falsebehavior, new GitHub releases are public before npm succeeds, so a new push or rerunning all jobs can skip an already-released version. If only finalization fails, retry that job without republishing npm.Reference: https://github.com/dev-five-git/csstype-extra/blob/main/.github/workflows/publish.yml
Successful reference run: https://github.com/dev-five-git/csstype-extra/actions/runs/29142929643
Incident: https://github.com/dev-five-git/bun-test-env-dom/actions/runs/34464132018/job/102828597908
Actual OIDC publication has not been triggered; merging this workflow change will run it on main.