Add SwiftPM release packaging + workflow #52
Merged
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.
Description
Adds a public SwiftPM entry at the repo root using a binary target that points to a release asset zip, this will let folks not have to use a local script if they are wanting to use swift bindings, they can just point to this repo using Swift Package Manager.
Notes to the reviewers
This is a bit different way to do this from bdk-ffi, with this we dont need to create a separate rust-ctktap-swift repo or anything.
Also of note, preferred way to do a rust-cktap release now that will cut the release and also create+tag a Swift Package is to run the “Release Swift Package” workflow with a tag like v0.1.1 (or 0.1.1), which will build the xcframework, zip it, update Package.swift, commit the Swift sources, tags, and upload the asset.
Changelog notice
Checklists
All Submissions:
cargo fmtandcargo clippybefore committingNew Features:
Bugfixes: