Repository navigation
chore: prepare React Native bindings 1.17.1 - #16
Merged
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
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.
Upgrade the package and locked Rust/FFI core to 1.17.1. Regenerate TypeScript and C++ bindings from the actual published FFI library, including pending-update export and fallible JSON export APIs. Correct repository metadata after the move to loro-dev.
Add a tagged release workflow that builds release libraries for iOS and Android, assembles the generated bindings and platform artifacts, typechecks and builds the JS package, and rejects an npm tarball missing either platform before publishing. Publishing uses an existing NPM_TOKEN or npm trusted publishing; this machine currently has no npm login.
Validation: the host native library built against locked registry dependencies; TypeScript typecheck and the full builder-bob preparation (JS, declarations, native codegen) passed. actionlint validated the release workflow. Device artifacts are built and verified by the new release workflow before upload to npm.