fix: bump rive-android to 11.9.1 and rive-ios to 6.23.1 - #370
Merged
Conversation
Bumps the pinned native runtimes on the 0.4.x line to the latest releases: rive-android 11.7.2 -> 11.9.1 and rive-ios 6.21.1 -> 6.23.1. Also points this branch's release-please workflow at release-v0.4 so the 0.4.x line keeps cutting stable releases to the npm latest tag while main produces 0.5.0 betas.
mfazekas
pushed a commit
that referenced
this pull request
Aug 19, 2026
🤖 I have created a release *beep* *boop* --- ## [0.4.20](v0.4.19...v0.4.20) (2026-08-19) ### Bug Fixes * bump rive-android to 11.9.1 and rive-ios to 6.23.1 ([#370](#370)) ([ae1fdb9](ae1fdb9)) --- 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
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.
Ports the runtime bump from #367 to the stable 0.4.x line: rive-android 11.7.2 → 11.9.1 and rive-ios 6.21.1 → 6.23.1.
Only
package.jsonneeds changing here. The other two files in #367 (android/src/new/...andios/new/RiveRuntimeLogger.swift) arrived with the breakingfeat!: experimental Rive runtime backend(#134) that started the 0.5.0-beta line, so they don't exist on this branch.Also points this branch's copy of the release-please workflow at
release-v0.4. Withouttarget-branchthe action reads its config and manifest from the repository's default branch and would cut a 0.5.0-beta; a push only ever triggers the workflow file on the branch pushed, somainkeeps producing betas unchanged. The branch was cut fromv0.4.19, which already carries a non-prerelease release-please config and a manifest at0.4.19, so no config changes were needed. Merging this should produce a0.4.20release PR, and a non-prerelease GitHub release publishes to the npmlatesttag via the existing conditional inpublish.yml.On verification, I could not get a green local run on this branch — but nothing I found is attributable to the bump, and each failure reproduces identically at the old pins:
constevalerror inPods/fmt/include/fmt/format-inl.h.maincarries a Podfile fix for this that this branch predates. Confirmed pre-existing by a cleanpod install+ build with RiveRuntime pinned back to 6.21.1 — identical errors.viewmodel-properties › non-existent properties return undefinedfails. Confirmed pre-existing at rive-android 11.7.2 — identical failure.bad color buffer handle, a gfxstream host-GPU crash), taking ~10 suites down withadberrors rather than assertion failures. Reproduced at 11.7.2 as well, on a cold-booted emulator.What did verify cleanly: Android compiles against 11.9.1 with zero deprecation warnings (this tree predates the API surface 11.9.x deprecates), and
pod installresolves RiveRuntime 6.23.1. CI is the meaningful gate here, since it runs a different Xcode and emulator image.