Repository navigation
chore(release): version packages - #469
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
September 23, 2026 07:35
e2c50ff to
8571765
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 07:48
8571765 to
1fd4ebf
Compare
hurali97
approved these changes
Sep 24, 2026
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
brownfield@5.1.1
Patch Changes
@callstack/brownfield-navigation@5.1.1
Patch Changes
@callstack/brownie@5.1.1
Patch Changes
@callstack/react-native-brownfield@5.1.1
Patch Changes
#458
bf976fdThanks @KisaneNeko! - Bump the Brownfield Gradle Plugin version injected by the Expo config plugin to2.0.0-alpha09.#462
2f7d5daThanks @likevy! - fixes #457, android back callbacks survived RN fragment view destruction, retaining delegates and intercepting back presses after re-entry#470
09162c2Thanks @KisaneNeko! - FixpopToNative()on iOS closing every React Native screen instead of only the topmost one.popToNative()is delivered as an app-wide notification, so every live React Native surface acted on it — including surfaces buried under other screens, and each surface acted twice when hosted by SwiftUI. In a stack such as RN → native → RN, a single call tore down the whole navigation stack, taking native screens with it.A React Native surface now acts only when it is the topmost one on screen, and only once per host.
Two consequences worth knowing about:
popToNative()is now a no-op instead of popping the hidden screen. It logs when this happens.popToNative()no longer dismisses a modally presented native screen that merely contains a React Native surface. Only a surface that owns a navigation stack entry pops.Updated dependencies []:
@callstack/brownfield-cli@5.1.1