Repository navigation
fix: bump rive-android to 11.12.1 and rive-ios to 6.26.0 - #397
Merged
Merged
Conversation
mfazekas
added a commit
that referenced
this pull request
Sep 28, 2026
Ports the runtime bump from #397 to the stable 0.4.x line: rive-android 11.9.1 → 11.12.1 and rive-ios 6.23.1 → 6.26.0. Only `package.json` changes here, as in #370. rive-ios 6.27.0 isn't on CocoaPods trunk yet, so 6.26.0 is the newest the podspec can use. 11.12.1 fixes the CheckJNI abort that 11.10.0–11.12.0 hit when a nonexistent boolean view-model property is read (rive-android#470). 11.11.0 deprecates the legacy `app.rive.runtime.kotlin` API this line is built on; that's a compile warning only, nothing is removed. Verified locally: the Android example resolves `app.rive:rive-android:11.12.1` and builds, and the Android harness passes (16/16 suites, 76 passed + 3 skipped on a Pixel 6 emulator). The iOS example on this branch still doesn't build locally on Xcode 26.5 (RN 0.79's fmt `consteval` error, unrelated to the bump), so CI is the gate for iOS; the same 6.26.0 pod builds and passes the harness on both backends in #397.
Bumps the pinned native runtimes: rive-android 11.9.1 → 11.12.1 and rive-ios 6.23.1 → 6.26.0. rive-ios 6.27.0 is on GitHub but not on CocoaPods trunk, so 6.26.0 is the newest release the podspec can use. 11.12.1 is the first rive-android release since 11.9.1 that is safe to pin: 11.10.0–11.12.0 abort debuggable apps under CheckJNI when a nonexistent boolean view-model property is read (rive-android#470). The range brings accessibility semantics, file asset metadata, GPU Canvas (off by default), referenced-asset updates for loaded files, Unicode line breaking and a batch of resource-cleanup and rendering fixes; 6.24–6.26 bring the matching core runtime fixes on iOS. rive-android 11.11.0 deprecates the legacy app.rive.runtime.kotlin API (RiveAnimationView, state machine inputs, events, text runs) that the legacy backend uses, and 11.12 adds more 12.0 deprecations on the new API. Both are compile warnings only; nothing is removed.
mfazekas
force-pushed
the
claude/bump-rive-runtimes
branch
from
September 29, 2026 10:55
0fb333d to
1906dc8
Compare
Drop the beta prerelease settings and pin the next release to 0.5.0. release-as must be removed after 0.5.0 is published.
mfazekas
pushed a commit
that referenced
this pull request
Sep 29, 2026
🤖 I have created a release *beep* *boop* --- ## [0.5.0](v0.5.0-beta.6...v0.5.0) (2026-09-29) ### ⚠ BREAKING CHANGES * rename RiveAsset to RiveFileSource ([#391](#391)) * generate referenced asset names in .riv schemas, type referencedAssets ([#359](#359)) ### Features * generate referenced asset names in .riv schemas, type referencedAssets ([#359](#359)) ([dad0bf0](dad0bf0)) ### Bug Fixes * bump rive-android to 11.12.1 and rive-ios to 6.26.0 ([#397](#397)) ([24f3df0](24f3df0)) ### Code Refactoring * rename RiveAsset to RiveFileSource ([#391](#391)) ([7e9786a](7e9786a)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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
2 participants
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.
Bumps the pinned native runtimes to the newest releases we can consume: rive-android 11.9.1 → 11.12.1 and rive-ios 6.23.1 → 6.26.0. rive-ios 6.27.0 is tagged on GitHub but was never pushed to CocoaPods trunk, which tops out at 6.26.0, so the podspec can't use it yet.
11.12.1 is also the first safe rive-android pin after 11.9.1: 11.10.0–11.12.0 abort debuggable apps under CheckJNI when a nonexistent boolean view-model property is read (rive-android#470, fixed in 11.12.1). 11.11.0 deprecates the legacy
app.rive.runtime.kotlinAPI the legacy backend uses, and 11.12 adds more 12.0 deprecations on the new API; both are compile warnings only, nothing is removed. The only other change is the rive-ios source link inRiveRuntimeLogger.swift, repointed at the same lines in 6.26.0.Verified locally, both backends on both platforms (iPhone 17 simulator, Pixel 6 emulator):
#381 pins the same versions, so it will rebase cleanly once this lands. The 0.4.x counterpart is a separate PR against
release-v0.4.Also switches release-please from beta prereleases to a final release pinned at
0.5.0, so the release PR after this merges is 0.5.0 and publishes to npmlatest.release-ashas to be removed once 0.5.0 is out.