Repository navigation
馃敡 Fix Swift SDK release publishing - #367
Merged
Merged
Conversation
Use a Node runtime supported by npm trusted publishing and update the release action. Allow a tagged Swift release to resume after a publish or GitHub release failure without creating a second version.
The current version mismatch is fixed by publishing a new Swift release. Remove the one-off resume path and keep the same version-bump flow used by other clients.
Robdel12
changed the title
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 Swift SDK ships as both an npm package and a SwiftPM package. A new release needs the npm package and SwiftPM tags to carry the same version and source. npm Trusted Publishing requires Node.js 22.14 or later; the publishing workflows were pinned to 22.13.1.
What changed
swift/vX.Y.ZandvX.Y.Ztags together.Confidence
Swift and Swift CLI plugin tests pass. Release workflow YAML and embedded shell scripts parse. A live publish was not run; it requires npm Trusted Publisher and GitHub release configuration.