Fix Components 4 publish recovery - #224
Merged
Merged
Conversation
Correct the malformed setup-node SHA, preserve explicit manual version publication after a release-only failure, and restore the repository's no-release merge guard.
This was referenced Aug 30, 2026
This was referenced Aug 30, 2026
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.
Summary
Repairs the Components 4 publication workflow after the GitHub release was created but npm publishing could not start.
Fixed
actions/setup-nodecommit pin that prevented the npm job from starting. (Prepare owner-authorized Components 4 publication #207)no-releasehandling for publication-workflow maintenance merges. (Prepare owner-authorized Components 4 publication #207)