release: v0.2.57 - #54
Merged
Merged
Conversation
Recovery release. The v0.2.56 run published system-canvas and system-canvas-react to npm but failed on system-canvas-standalone (transient OIDC token-exchange ENEEDAUTH on the 3rd sequential publish), so the version-bump push never ran and standalone stayed at 0.2.55. Bump all three to 0.2.57 so standalone catches up and the repo re-syncs with npm; core/react republish harmlessly at the new version.
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.
Recovery release
The
v0.2.56release run partially failed:The 3rd sequential OIDC
npm publish(standalone) hung ~70s then fell back to token auth and failed withENEEDAUTH— a transient OIDC token-exchange failure, not a config/secret issue (the first two publishes in the same job succeeded). Because the publish step failed, the finalgit pushof the version-bump commit never ran, leavingmainat 0.2.55 while npm has 0.2.56 for two packages.Fix
Explicit bump of all three packages to 0.2.57 (root version changed 0.2.55 -> 0.2.57 triggers the workflow's explicit-release mode, avoiding an auto-patch collision with the already-published 0.2.56). standalone catches up; core/react republish harmlessly at the new version; repo and npm re-sync.
No code changes — version/dep-range bumps only.