@react-navigation/stack@8.0.0-alpha.54

8.0.0-alpha.54 (2026-09-14)

• refactor!: use a render callback instead of NavigationContent for custom navigators (#13238) (c9c119e), closes #13238 - by @satya164

Bug Fixes

• avoid deprecated shadow style on web in stack (#13246) (d0b41e7) - by @satya164

BREAKING CHANGES

• this changes the API for custom navigators:

-const { NavigationContent } = useNavigationBuilder(Router, props);
+const { render } = useNavigationBuilder(Router, props);

-return (
-  <NavigationContent>
-    <NavigatorView />
-  </NavigationContent>
+return render(
+  <NavigatorView />
 );

custom navigators now must use the returned render function from
useNavigationBuilder instead of the NavigationContent.

the previous API isn't feasible while maintaining concurrent safety.

@react-navigation/native@8.0.0-alpha.45

8.0.0-alpha.45 (2026-09-14)

• refactor!: use a render callback instead of NavigationContent for custom navigators (#13238) (c9c119e), closes #13238 - by @satya164

Bug Fixes

• use reactApplicationContext.currentActivity in MaterialSymbolModule (#13235) (b0352b5) - by @eduardoborges

BREAKING CHANGES

• this changes the API for custom navigators:

-const { NavigationContent } = useNavigationBuilder(Router, props);
+const { render } = useNavigationBuilder(Router, props);

-return (
-  <NavigationContent>
-    <NavigatorView />
-  </NavigationContent>
+return render(
+  <NavigatorView />
 );

custom navigators now must use the returned render function from
useNavigationBuilder instead of the NavigationContent.

the previous API isn't feasible while maintaining concurrent safety.

@react-navigation/native-stack@8.0.0-alpha.53

8.0.0-alpha.53 (2026-09-14)

• refactor!: use a render callback instead of NavigationContent for custom navigators (#13238) (c9c119e), closes #13238 - by @satya164

BREAKING CHANGES

• this changes the API for custom navigators:

-const { NavigationContent } = useNavigationBuilder(Router, props);
+const { render } = useNavigationBuilder(Router, props);

-return (
-  <NavigationContent>
-    <NavigatorView />
-  </NavigationContent>
+return render(
+  <NavigatorView />
 );

custom navigators now must use the returned render function from
useNavigationBuilder instead of the NavigationContent.

the previous API isn't feasible while maintaining concurrent safety.

@react-navigation/material-top-tabs@8.0.0-alpha.50

8.0.0-alpha.50 (2026-09-14)

• refactor!: use a render callback instead of NavigationContent for custom navigators (#13238) (c9c119e), closes #13238 - by @satya164

BREAKING CHANGES

• this changes the API for custom navigators:

-const { NavigationContent } = useNavigationBuilder(Router, props);
+const { render } = useNavigationBuilder(Router, props);

-return (
-  <NavigationContent>
-    <NavigatorView />
-  </NavigationContent>
+return render(
+  <NavigatorView />
 );

custom navigators now must use the returned render function from
useNavigationBuilder instead of the NavigationContent.

the previous API isn't feasible while maintaining concurrent safety.

@react-navigation/elements@3.0.0-alpha.49

3.0.0-alpha.49 (2026-09-14)

• refactor!: use a render callback instead of NavigationContent for custom navigators (#13238) (c9c119e), closes #13238 - by @satya164

BREAKING CHANGES

• this changes the API for custom navigators:

-const { NavigationContent } = useNavigationBuilder(Router, props);
+const { render } = useNavigationBuilder(Router, props);

-return (
-  <NavigationContent>
-    <NavigatorView />
-  </NavigationContent>
+return render(
+  <NavigatorView />
 );

custom navigators now must use the returned render function from
useNavigationBuilder instead of the NavigationContent.

the previous API isn't feasible while maintaining concurrent safety.

@react-navigation/drawer@8.0.0-alpha.52

8.0.0-alpha.52 (2026-09-14)

• refactor!: use a render callback instead of NavigationContent for custom navigators (#13238) (c9c119e), closes #13238 - by @satya164

BREAKING CHANGES

• this changes the API for custom navigators:

-const { NavigationContent } = useNavigationBuilder(Router, props);
+const { render } = useNavigationBuilder(Router, props);

-return (
-  <NavigationContent>
-    <NavigatorView />
-  </NavigationContent>
+return render(
+  <NavigatorView />
 );

custom navigators now must use the returned render function from
useNavigationBuilder instead of the NavigationContent.

the previous API isn't feasible while maintaining concurrent safety.

@react-navigation/core@8.0.0-alpha.35

8.0.0-alpha.35 (2026-09-14)

• refactor!: use a render callback instead of NavigationContent for custom navigators (#13238) (c9c119e), closes #13238 - by @satya164

Bug Fixes

• allow removal prevention when navigation was suspended (#13244) (75ac425) - by @satya164
• avoid stale options events & notify when nested navigators are removed (#13245) (be48fea) - by @satya164
• deduplicate scheduled navigation updates (#13241) (92e57ea) - by @satya164
• fix more concurrent rendering issues in useNavigationState (#13239) (7685418) - by @satya164
• keep navigation and route stable after suspense (#13240) (6db6331) - by @satya164
• preserve navigator state across hidden activity updates (#13242) (2f02e12) - by @satya164
• use committed focus for events and effects (#13243) (c386bf0) - by @satya164

BREAKING CHANGES

• this changes the API for custom navigators:

-const { NavigationContent } = useNavigationBuilder(Router, props);
+const { render } = useNavigationBuilder(Router, props);

-return (
-  <NavigationContent>
-    <NavigatorView />
-  </NavigationContent>
+return render(
+  <NavigatorView />
 );

custom navigators now must use the returned render function from
useNavigationBuilder instead of the NavigationContent.

the previous API isn't feasible while maintaining concurrent safety.

@react-navigation/bottom-tabs@8.0.0-alpha.51

8.0.0-alpha.51 (2026-09-14)

• refactor!: use a render callback instead of NavigationContent for custom navigators (#13238) (c9c119e), closes #13238 - by @satya164

BREAKING CHANGES

• this changes the API for custom navigators:

-const { NavigationContent } = useNavigationBuilder(Router, props);
+const { render } = useNavigationBuilder(Router, props);

-return (
-  <NavigationContent>
-    <NavigatorView />
-  </NavigationContent>
+return render(
+  <NavigatorView />
 );

custom navigators now must use the returned render function from
useNavigationBuilder instead of the NavigationContent.

the previous API isn't feasible while maintaining concurrent safety.

@react-navigation/native@7.3.18

7.3.18 (2026-08-26)

Bug Fixes

• prevent state reset when history.go() takes longer than timeout on web (#13217) (1b309a7) - by @collectioneur

@react-navigation/native@8.0.0-alpha.44

8.0.0-alpha.44 (2026-08-26)

Bug Fixes

• prevent state reset when history.go() takes longer than timeout on web (#13217) (fc82c1b), closes #11145 - by @collectioneur