Repository navigation
release: prepare 0.1.3 Preview for CI publication - #67
Merged
Merged
Conversation
rdlabo
changed the title
rdlabo
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
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.
Prepare cf-workers-native 0.1.3 for publication to npm latest through the existing tag-triggered GitHub Actions Release workflow, with provenance. All 0.x releases are Preview releases; latest is an installation channel, not a production-stability claim.
Bump npm and Android source publication metadata to 0.1.3, update installation instructions to npm 0.1.3 and SwiftPM v0.1.3, and retain the documented compatibility limitations. Runtime/native implementation is unchanged. Existing Android native consumers can continue using Maven Central 0.1.2.
Local validation: npm release authorization/channel tests and Android publishing helper tests passed; formatting and whitespace checks passed. Publication requires successful Compatibility on the exact main commit. Existing v0.1.2 stays unchanged. The separately requested npm run release command is a follow-up change and is not included in this merged PR.