@W-23748894 chore(release): bump version to 4.3.24 to re-trigger npm publish - #83
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
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.
Why
The publish job for
4.3.23(merged in #82) failed with an npmE404onPUT @api-components/api-navigation— an expired/invalid publish token, which npm surfaces as a 404. The version bump landed onmainbut the package was never published to the registry.The token has since been renewed. npm does not allow re-publishing a version from an already-merged commit, so this PR bumps to
4.3.24purely to re-trigger thePublishing releaseworkflow with the working token. No functional changes.What
package.json:4.3.23→4.3.24package-lock.json: aligned root + root-packageversionto4.3.24(lockfile had lagged at4.3.22)Testing
No code changes; CI runs the existing suite. Publish step should now succeed with the renewed token.