[release-v1.17][npm]: Bump the major group across 5 directories with 34 updates

[dependabot]

Bumps the major group with 26 updates in the /backstage directory:

Package	From	To
@spotify/prettier-config	12.0.0	15.0.0
concurrently	8.2.2	9.1.2
lerna	7.4.2	8.2.1
node-gyp	9.4.1	11.1.0
prettier	2.8.8	3.5.3
react	17.0.2	19.0.0
react-dom	17.0.2	19.0.0
@types/react-dom	17.0.26	19.0.4
react-router	6.20.1	7.4.0
react-router-dom	6.20.1	7.4.0
@testing-library/jest-dom	5.17.0	6.6.3
@testing-library/react	12.1.5	16.2.0
@testing-library/dom	8.20.1	10.4.0
@backstage/plugin-search-backend	1.4.7	2.0.0
@backstage/plugin-techdocs-backend	1.9.0	2.0.0
better-sqlite3	9.2.2	11.9.1
dockerode	3.3.5	4.0.4
@types/express	4.17.21	5.0.1
@types/express-serve-static-core	4.17.41	5.0.6
@types/luxon	2.4.0	3.4.2
@backstage/backend-plugin-api	0.6.18	1.2.1
node-fetch	2.7.0	3.3.2
yn	4.0.0	5.0.0
@janus-idp/cli	1.8.7	3.3.1
msw	1.3.2	2.7.3
supertest	6.3.3	7.1.0

Bumps the major group with 7 updates in the /backstage/packages/app directory:

Package	From	To
react	17.0.2	19.0.0
react-dom	17.0.2	19.0.0
react-router	6.30.0	7.4.0
react-router-dom	6.30.0	7.4.0
@testing-library/jest-dom	5.17.0	6.6.3
@testing-library/react	12.1.5	16.2.0
@testing-library/dom	8.20.1	10.4.0

Bumps the major group with 7 updates in the /backstage/packages/backend directory:

Package	From	To
node-gyp	9.4.1	11.1.0
@backstage/plugin-search-backend	1.8.2	2.0.0
@backstage/plugin-techdocs-backend	1.11.6	2.0.0
better-sqlite3	9.6.0	11.9.1
dockerode	3.3.5	4.0.4
@types/express-serve-static-core	4.19.6	5.0.6
@types/luxon	2.4.0	3.4.2

Bumps the major group with 7 updates in the /backstage/plugins/knative-event-mesh-backend directory:

Package	From	To
@backstage/backend-plugin-api	0.6.21	1.2.1
node-fetch	2.7.0	3.3.2
yn	4.0.0	5.0.0
@janus-idp/cli	1.19.1	3.3.1
@types/supertest	2.0.16	6.0.3
msw	1.3.5	2.7.3
supertest	6.3.4	7.1.0

Bumps the major group with 3 updates in the /backstage/plugins/knative-event-mesh-backend/dist-dynamic directory: @types/express-serve-static-core, node-fetch and yn.

Updates @spotify/prettier-config from 12.0.0 to 15.0.0

Release notes

Sourced from @​spotify/prettier-config's releases.

v15.0.0

15.0.0 (2023-05-18)

chore

• deps: upgrade dependencies (ef060c7)
• node: upgrade required Node version to 18 (9528841)

BREAKING CHANGES

• node: Node bump from v14 to v18
• deps: TypeScript bump from v4 to v5, Jest bump from v28 to v29

v14.1.6

14.1.6 (2023-02-14)

Bug Fixes

• update dependencies (5c7d2ed)

v14.1.5

14.1.5 (2023-01-30)

Bug Fixes

• update dependencies (32226e3)

v14.1.4

14.1.4 (2023-01-19)

Bug Fixes

• update dependencies (ecac663)

v14.1.3

14.1.3 (2022-12-07)

Bug Fixes

• dependency updates (98dcee7)

v14.1.2

14.1.2 (2022-12-02)

... (truncated)

Changelog

Sourced from @​spotify/prettier-config's changelog.

15.0.0 (2023-05-18)

chore

• deps: upgrade dependencies (ef060c7)
• node: upgrade required Node version to 18 (9528841)

BREAKING CHANGES

• node: Node bump from v14 to v18
• deps: TypeScript bump from v4 to v5, Jest bump from v28 to v29

14.1.6 (2023-02-14)

Bug Fixes

• update dependencies (5c7d2ed)

14.1.5 (2023-01-30)

Bug Fixes

• update dependencies (32226e3)

14.1.4 (2023-01-19)

Bug Fixes

• update dependencies (ecac663)

14.1.3 (2022-12-07)

Bug Fixes

• dependency updates (98dcee7)

14.1.2 (2022-12-02)

Bug Fixes

• web-scripts: security vulnerability in glob (a278f21)

14.1.1 (2022-11-25)

Bug Fixes

• precommit: add in --passWithNoTests flag to enable precommit hook to succeed with no tests (67cba2a), closes #1020

14.1.0 (2022-08-08)

... (truncated)

Commits

• 6d8c063 v15.0.0
• 6519dca Merge pull request #1128 from nlebrun-spotify/upgrade-dependencies
• 9528841 chore(node): upgrade required Node version to 18
• ef060c7 chore(deps): upgrade dependencies
• cfb9c66 v14.1.6
• 7b2160e Merge pull request #1105 from spotify/cut-new-release
• 5c7d2ed fix: update dependencies
• a31d65c Merge pull request #1100 from spotify/dependabot/npm_and_yarn/commitizen-4.3.0
• 07db5cf Merge pull request #1103 from spotify/dependabot/npm_and_yarn/http-cache-sema...
• 7925f32 Create catalog-info.yaml
• Additional commits viewable in compare view

Updates concurrently from 8.2.2 to 9.1.2

Release notes

Sourced from concurrently's releases.

v9.1.2

What's Changed

• Add ability to have custom logger by @​mwood23 in open-cli-tools/concurrently#522

New Contributors

• @​mwood23 made their first contribution in open-cli-tools/concurrently#522

Full Changelog: open-cli-tools/concurrently@v9.1.1...v9.1.2

v9.1.1

What's Changed

• fix: support Deno's JSON with comments configuration by @​mahtaran in open-cli-tools/concurrently#523

Full Changelog: open-cli-tools/concurrently@v9.1.0...v9.1.1

v9.1.0

What's Changed

• Remove signal event listeners on finish by @​gustavohenke in open-cli-tools/concurrently#512
• Add support for Deno shortcuts and wildcards by @​mahtaran in open-cli-tools/concurrently#508
• bin: show help when no args are passed by @​gustavohenke in open-cli-tools/concurrently#513

New Contributors

• @​mahtaran made their first contribution in open-cli-tools/concurrently#508

Full Changelog: open-cli-tools/concurrently@v9.0.1...v9.1.0

v9.0.1

What's Changed

• Don't set up more than 1 abort signal listener by @​gustavohenke in open-cli-tools/concurrently#503

Full Changelog: open-cli-tools/concurrently@v9.0.0...v9.0.1

v9.0.0

💥 Breaking Changes

• Dropped support for Node.js < 18.0.0. Older Node.js version have reached end-of-life, and certain features require new-ish JS APIs.

• Pending commands no longer run when --max-processes is set and an interruption/kill signal is sent - #433, #452, #460 Before v9.0.0, pressing Ctrl+C when --max-processes is set meant that only those commands would receive it. Once these stopped, the pending commands would start, which in turn meant that another Ctrl+C press would be necessary to stop them, and so on. Similar situation applied to combining --max-processes with --kill-others/--kill-others-on-fail.

  Starting with v9.0.0, this no longer happens, as these flags and/or key presses send a signal to stop the running commands in addition to preventing new commands from running.

• The concurrently and default exports are now the same - #399 It's reasonable to expect that import { concurrently } from 'concurrently' would work the same as import concurrently from 'concurrently', however this has not been the case. The former used to be an unconfigured version of concurrently, lacking all features that you'd get from the CLI, which was seen as a "footgun". Both are now the same function.

  If you'd like to access the unconfigured function, use import { createConcurrently } from 'concurrently' instead.

✨ New Features

... (truncated)

Commits

• 7f3efb2 9.1.2
• 36eccae Add ability to have custom logger (#522)
• 6cafc60 9.1.1
• 80fceda fix: support Deno's JSON with comments (#523)
• 8d3f976 docs: fix inconsistencies in passthrough args page
• e3a76f7 9.1.0
• b358954 bin: show help when no args are passed (#513)
• 64b7e2a Add support for Deno shortcuts and wildcards (#508)
• 3bcc9c9 Remove signal event listeners from process on finish (#512)
• 79b3290 9.0.1
• Additional commits viewable in compare view

Updates lerna from 7.4.2 to 8.2.1

Release notes

Sourced from lerna's releases.

v8.2.1

8.2.1 (2025-03-03)

Note: Version bump only for package lerna-monorepo

v8.2.0

8.2.0 (2025-02-19)

Bug Fixes

• drop strip-ansi in favor of native stripVTControlCharacters (#4095) (9e4ac9c)

Features

• allow custom working dir for detectProjects (#4148) (08d1d0d)

v8.1.9

8.1.9 (2024-10-31)

Bug Fixes

• add extends property in schema (#4075) (28c8ef2)
• core: avoid reading empty .config.json, upgrade [email protected] (#4062) (960bdd9)
• update nx support to latest v20 (#4103) (cb37f19)
• version: enable changing commit message when using amend (#3954) (529e83f)

Features

• publish: support full file path for --summary-file (#4039) (cfd573a)

v8.1.8

8.1.8 (2024-08-05)

Bug Fixes

• publish: upgrade @​npmcli/arborist to 7.5.4 (#4058) (89de0eb)
• version: truncate release body based on maximum size allowed by VCS client (#4041) (3c2a3c9)

Features

• publish: enable throttling when publishing modules (#4013) (fccca12)

v8.1.7

8.1.7 (2024-07-21)

... (truncated)

Changelog

Sourced from lerna's changelog.

8.2.1 (2025-03-03)

Note: Version bump only for package lerna

8.2.0 (2025-02-19)

Bug Fixes

• drop strip-ansi in favor of native stripVTControlCharacters (#4095) (9e4ac9c)

Features

• allow custom working dir for detectProjects (#4148) (08d1d0d)

8.1.9 (2024-10-31)

Bug Fixes

• add extends property in schema (#4075) (28c8ef2)
• core: avoid reading empty .config.json, upgrade [email protected] (#4062) (960bdd9)
• update nx support to latest v20 (#4103) (cb37f19)

8.1.8 (2024-08-05)

Bug Fixes

• publish: upgrade @​npmcli/arborist to 7.5.4 (#4058) (89de0eb)

8.1.7 (2024-07-21)

Bug Fixes

• set explicit strip-ansi dependency (#4045) (6e5cfbc)

8.1.6 (2024-07-05)

Bug Fixes

• set explicit string-width dependency (#4038) (5f3603a)

8.1.5 (2024-06-24)

Bug Fixes

• update npm utility dependencies and related packages (#4033) (bd1c2d8)

8.1.4 (2024-06-09)

Note: Version bump only for package lerna

... (truncated)

Commits

• 95ab1cb chore(misc): publish 8.2.1
• 770220c chore(deps): bump @​octokit/rest from 19.0.11 to 20.1.2 (#4154)
• 58cdfec chore(misc): publish 8.2.0
• 08d1d0d feat: allow custom working dir for detectProjects (#4148)
• 0dd2cb9 chore: update to latest dependencies (#4151)
• 9e4ac9c fix: drop strip-ansi in favor of native stripVTControlCharacters (#4095)
• 7d1338d chore(misc): publish 8.1.9
• cb37f19 fix: update nx support to latest v20 (#4103)
• 28c8ef2 fix: add extends property in schema (#4075)
• 960bdd9 fix(core): avoid reading empty .config.json, upgrade [email protected] (#4062)
• Additional commits viewable in compare view

Updates node-gyp from 9.4.1 to 11.1.0

Release notes

Sourced from node-gyp's releases.

v11.1.0

11.1.0 (2025-02-10)

Features

• update gyp-next to v0.19.1 (#3122) (504250e)

Bug Fixes

• Find VC.Tools.ARM64 on arm64 machine (#3075) (b899fae)
• try libnode.dll first in load_exe_hook (#2834) (b9d10a5)

Miscellaneous

• add gyp-next updater (#3105) (e3f9a77)
• Test on Ubuntu-24.04-arm and Node.js v23 (#3121) (2530f51)
• Use astral-sh/ruff-action@v3 to run the Python linter (#3114) (94448fc)

v11.0.0

11.0.0 (2024-12-03)

⚠ BREAKING CHANGES

• drop node 16 support (#3102)

Features

• drop node 16 support (#3102) (0e6b6f8)

Miscellaneous

• migrate from standard to neostandard (#3103) (a130178)

v10.3.1

10.3.1 (2024-12-02)

Miscellaneous

• fix npm-publish dependencies and add provenance (#3099) (6dded88)

v10.3.0

10.3.0 (2024-11-29)

... (truncated)

Changelog

Sourced from node-gyp's changelog.

11.1.0 (2025-02-10)

Features

• update gyp-next to v0.19.1 (#3122) (504250e)

Bug Fixes

• Find VC.Tools.ARM64 on arm64 machine (#3075) (b899fae)
• try libnode.dll first in load_exe_hook (#2834) (b9d10a5)

Miscellaneous

• add gyp-next updater (#3105) (e3f9a77)
• Test on Ubuntu-24.04-arm and Node.js v23 (#3121) (2530f51)
• Use astral-sh/ruff-action@v3 to run the Python linter (#3114) (94448fc)

11.0.0 (2024-12-03)

⚠ BREAKING CHANGES

• drop node 16 support (#3102)

Features

• drop node 16 support (#3102) (0e6b6f8)

Miscellaneous

• migrate from standard to neostandard (#3103) (a130178)

10.3.1 (2024-12-02)

Miscellaneous

• fix npm-publish dependencies and add provenance (#3099) (6dded88)

10.3.0 (2024-11-29)

Features

• prohibit compiling with ClangCL on Windows (#3098) (88260bf)

... (truncated)

Commits

• b5f34c0 chore(main): release 11.1.0 (#3110)
• 504250e feat: update gyp-next to v0.19.1 (#3122)
• 2530f51 chore: Test on Ubuntu-24.04-arm and Node.js v23 (#3121)
• e3f9a77 chore: add gyp-next updater (#3105)
• 44cea2e Test on GitHub Actions windows-2025 image (#3116)
• 94448fc chore: Use astral-sh/ruff-action@v3 to run the Python linter (#3114)
• b899fae fix: Find VC.Tools.ARM64 on arm64 machine (#3075)
• b9d10a5 fix: try libnode.dll first in load_exe_hook (#2834)
• bf9168e chore(main): release 11.0.0 (#3104)
• a130178 chore: migrate from standard to neostandard (#3103)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by nodejs-foundation, a new releaser for node-gyp since your current version.

Updates prettier from 2.8.8 to 3.5.3

Release notes

Sourced from prettier's releases.

3.5.3

🔗 Changelog

3.5.2

🔗 Changelog

3.5.1

🔗 Changelog

3.5.0

diff

🔗 Release note

3.4.2

🔗 Changelog

3.4.1

🔗 Changelog

3.4.0

diff

🔗 Release note

3.3.3

🔗 Changelog

3.3.2

🔗 Changelog

3.3.1

🔗 Changelog

3.3.0

diff

🔗 Release note

3.2.5

🔗 Changelog

3.2.4

• Fix .eslintrc.json format #15947

🔗 Changelog

3.2.3

• Format tsconfig.json file with jsonc parser #15927

... (truncated)

Changelog

Sourced from prettier's changelog.

3.5.3

diff

Flow: Fix missing parentheses in ConditionalTypeAnnotation (#17196 by @​fisker)

// Input
type T<U> = 'a' | ('b' extends U ? 'c' : empty);
type T<U> = 'a' & ('b' extends U ? 'c' : empty);
// Prettier 3.5.2
type T<U> = "a" | "b" extends U ? "c" : empty;
type T<U> = "a" & "b" extends U ? "c" : empty;
// Prettier 3.5.3
type T<U> = "a" | ("b" extends U ? "c" : empty);
type T<U> = "a" & ("b" extends U ? "c" : empty);

3.5.2

diff

Remove module-sync condition (#17156 by @​fisker)

In Prettier 3.5.0, we added module-sync condition to package.json, so that require("prettier") can use ESM version, but turns out it doesn't work if CommonJS and ESM plugins both imports builtin plugins. To solve this problem, we decide simply remove the module-sync condition, so require("prettier") will still use the CommonJS version, we'll revisit until require(ESM) feature is more stable.

3.5.1

diff

Fix CLI crash when cache for old version exists (#17100 by @​sosukesuzuki)

Prettier 3.5 uses a different cache format than previous versions, Prettier 3.5.0 crashes when reading existing cache file, Prettier 3.5.1 fixed the problem.

Support dockercompose and github-actions-workflow in VSCode (#17101 by @​remcohaszing)

Prettier now supports the dockercompose and github-actions-workflow languages in Visual Studio Code.

3.5.0

diff

🔗 Release Notes

3.4.2

diff

... (truncated)

Commits

• 4ff5dc5 Release 3.5.3
• a2e560e Fix missing parentheses in ConditionalTypeAnnotation (#17196)
• fa95c97 Add mergeBlogPost step to release script (#17199)
• b47cd50 Add title to patch release changelog (#17197)
• de30788 Minor fix in release script
• ecee6a0 Clean changelog_unreleased
• fd06512 Bump Prettier dependency to 3.5.2
• 1f74dd5 Update dependents count
• 399f427 Release 3.5.2
• bf5aab8 Revert "Use ESM entrypoint for require(ESM)" (#17156)
• Additional commits viewable in compare view

Updates react from 17.0.2 to 19.0.0

Release notes

Sourced from react's releases.

19.0.0 (December 5, 2024)

Below is a list of all new features, APIs, deprecations, and breaking changes. Read React 19 release post and React 19 upgrade guide for more information.

Note: To help make the upgrade to React 19 easier, we’ve published a [email protected] release that is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19. We recommend upgrading to React 18.3.1 first to help identify any issues before upgrading to React 19.

New Features

React

• Actions: startTransition can now accept async functions. Functions passed to startTransition are called “Actions”. A given Transition can include one or more Actions which update state in the background and update the UI with one commit. In addition to updating state, Actions can now perform side effects including async requests, and the Action will wait for the work to finish before finishing the Transition. This feature allows Transitions to include side effects like fetch() in the pending state, and provides support for error handling, and optimistic updates.
• useActionState: is a new hook to order Actions inside of a Transition with access to the state of the action, and the pending state. It accepts a reducer that can call Actions, and the initial state used for first render. It also accepts an optional string that is used if the action is passed to a form action prop to support progressive enhancement in forms.
• useOptimistic: is a new hook to update state while a Transition is in progress. It returns the state, and a set function that can be called inside a transition to “optimistically” update the state to expected final value immediately while the Transition completes in the background. When the transition finishes, the state is updated to the new value.
• use: is a new API that allows reading resources in render. In React 19, use accepts a promise or Context. If provided a promise, use will suspend until a value is resolved. use can only be used in render but can be called conditionally.
• ref as a prop: Refs can now be used as props, removing the need for forwardRef.
• Suspense sibling pre-warming: When a component suspends, React will immediately commit the fallback of the nearest Suspense boundary, without waiting for the entire sibling tree to render. After the fallback commits, React will schedule another render for the suspended siblings to “pre-warm” lazy requests.

React DOM Client

• <form> action prop: Form Actions allow you to manage forms automatically and integrate with useFormStatus. When a <form> action succeeds, React will automatically reset the form for uncontrolled components. The form can be reset manually with the new requestFormReset API.
• <button> and <input> formAction prop: Actions can be passed to the formAction prop to configure form submission behavior. This allows using different Actions depending on the input.
• useFormStatus: is a new hook that provides the status of the parent <form> action, as if the form was a Context provider. The hook returns the values: pending, data, method, and action.
• Support for Document Metadata: We’ve added support for rendering document metadata tags in components natively. React will automatically hoist them into the <head> section of the document.
• Support for Stylesheets: React 19 will ensure stylesheets are inserted into the <head> on the client before revealing the content of a Suspense boundary that depends on that stylesheet.
• Support for async scripts: Async scripts can be rendered anywhere in the component tree and React will handle ordering and deduplication.
• Support for preloading resources: React 19 ships with preinit, preload, prefetchDNS, and preconnect APIs to optimize initial page loads by moving discovery of additional resources like fonts out of stylesheet loading. They can also be used to prefetch resources used by an anticipated navigation.

React DOM Server

• Added prerender and prerenderToNodeStream APIs for static site generation. They are designed to work with streaming environments like Node.js Streams and Web Streams. Unlike renderToString, they wait for data to load for HTML generation.

React Server Components

• RSC features such as directives, server components, and server functions are now stable. This means libraries that ship with Server Components can now target React 19 as a peer dependency with a react-server export condition for use in frameworks that support the Full-stack React Architecture. The underlying APIs used to implement a React Server Components bundler or framework do not follow semver and may break between minors in React 19.x. See docs for how to support React Server Components.

Deprecations

• Deprecated: element.ref access: React 19 supports ref as a prop, so we’re deprecating element.ref in favor of element.props.ref. Accessing will result in a warning.
• react-test-renderer: In React 19, react-test-renderer logs a deprecation warning and has switched to concurrent rendering for web usage. We recommend migrating your tests to @​testinglibrary.com/docs/react-testing-library/intro/) or @​testingesting-library.com/docs/react-native-testing-library/intro)

Breaking Changes

React 19 brings in a number of breaking changes, including the removals of long-deprecated APIs. We recommend first upgrading to 18.3.1, where we've added additional deprecation warnings. Check out the upgrade guide for more details and guidance on codemodding.

React

• New JSX Transform is now required: We introduced a new JSX transform in 2020 to improve bundle size and use JSX without importing React. In React 19, we’re adding additional improvements like using ref as a prop and JSX speed improvements that require the new transform.
• Errors in render are not re-thrown: Errors that are not caught by an Error Boundary are now reported to window.reportError. Errors that are caught by an Error Boundary are reported to console.error. We’ve introduced onUncaughtError and onCaughtError methods to createRoot and hydrateRoot to customize this error handling.
• Removed: propTypes: Using propTypes will now be silently ignored. If required, we recommend migrating to TypeScript or another type-checking solution.
• Removed: defaultProps for functions: ES6 default parameters can be used in place. Class components continue to support defaultProps since there is no ES6 alternative.
• Removed: contextTypes and getChildContext: Legacy Context for class components has been removed in favor of the contextType API.

... (truncated)

Changelog

Sourced from react's changelog.

19.0.0 (December 5, 2024)

Below is a list of all new features, APIs, deprecations, and breaking changes. Read React 19 release post and React 19 upgrade guide for more information.

Note: To help make the upgrade to React 19 easier, we’ve published a [email protected] release that is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19. We recommend upgrading to React 18.3.1 first to help identify any issues before upgrading to React 19.

New Features

React

• Actions: startTransition can now accept async functions. Functions passed to startTransition are called “Actions”. A given Transition can include one or more Actions which update state in the background and update the UI with one commit. In addition to updating state, Actions can now perform side effects including async requests, and the Action will wait for the work to finish before finishing the Transition. This feature allows Transitions to include side effects like fetch() in the pending state, and provides support for error handling, and optimistic updates.
• useActionState: is a new hook to order Actions inside of a Transition with access to the state of the action, and the pending state. It accepts a reducer that can call Actions, and the initial state used for first render. It also accepts an optional string that is used if the action is passed to a form action prop to support progressive enhancement in forms.
• useOptimistic: is a new hook to update state while a Transition is in progress. It returns the state, and a set function that can be called inside a transition to “optimistically” update the state to expected final value immediately while the Transition completes in the background. When the transition finishes, the state is updated to the new value.
• use: is a new API that allows reading resources in render. In React 19, use accepts a promise or Context. If provided a promise, use will suspend until a value is resolved. use can only be used in render but can be called conditionally.
• ref as a prop: Refs can now be used as props, removing the need for forwardRef.
• Suspense sibling pre-warming: When a component suspends, React will immediately commit the fallback of the nearest Suspense boundary, without waiting for the entire sibling tree to render. After the fallback commits, React will schedule another render for the suspended siblings to “pre-warm” lazy requests.

React DOM Client

• <form> action prop: Form Actions allow you to manage forms automatically and integrate with useFormStatus. When a <form> action succeeds, React will automatically reset the form for uncontrolled components. The form can be reset manually with the new requestFormReset API.
• <button> and <input> formAction prop: Actions can be passed to the formAction prop to configure form submission behavior. This allows using different Actions depending on the input.
• useFormStatus: is a new hook that provides the status of the parent <form> action, as if the form was a Context provider. The hook returns the values: pending, data, method, and action.
• Support for Document Metadata: We’ve added support for rendering document metadata tags in components natively. React will automatically hoist them into the <head> section of the document.
• Support for Stylesheets: React 19 will ensure stylesheets are inserted into the <head> on the client before revealing the content of a Suspense boundary that depends on that stylesheet.
• Support for async scripts: Async scripts can be rendered anywhere in the component tree and React will handle ordering and deduplication.
• Support for preloading resources: React 19 ships with preinit, preload, prefetchDNS, and preconnect APIs to optimize initial page loads by moving discovery of additional resources like fonts out of stylesheet loading. They can also be used to prefetch resources used by an anticipated navigation.

React DOM Server

• Added prerender and prerenderToNodeStream APIs for static site generation. They are designed to work with streaming environments like Node.js Streams and Web Streams. Unlike renderToString, they wait for data to load for HTML generation.

React Server Components

• RSC features such as directives, server components, and server functions are now stable. This means libraries that ship with Server Components can now target React 19 as a peer dependency with a react-server export condition for use in frameworks that support the Full-stack React Architecture. The underlying APIs used to implement a React Server Components bundler or framework do not follow semver and may break between minors in React 19.x. See docs for how to support React Server Components.

Deprecations

• Deprecated: element.ref access: React 19 supports ref as a prop, so we’re deprecating element.ref in favor of element.props.ref. Accessing will result in a warning.
• react-test-renderer: In React 19, react-test-renderer logs a deprecation warning and has switched to concurrent rendering for web usage. We recommend migrating your tests to @​testing-library/react or @​testing-library/react-native

Breaking Changes

React 19 brings in a number of breaking changes, including the removals of long-deprecated APIs. We recommend first upgrading to 18.3.1, where we've added additional deprecation warnings. Check out the upgrade guide for more details and guidance on codemodding.

React

• New JSX Transform is now required: We introduced a new JSX transform in 2020 to improve bundle size and use JSX without importing React. In React 19, we’re adding additional improvements like using ref as a prop and JSX speed improvements that require the new transform.
• Errors in render are not re-thrown: Errors that are not caught by an Error Boundary are now reported to window.reportError. Errors that are caught by an Error Boundary are reported to console.error. We’ve introduced onUncaughtError and onCaughtError methods to createRoot and hydrateRoot to customize this error handling.
• Removed: propTypes: Using propTypes will now be silently ignored. If required, we recommend migrating to TypeScript or another type-checking solution.
• Removed: defaultProps for functions: ES6 default parameters can be used in place. Class components continue to support defaultProps since there is no ES6 alternative.

... (truncated)

Commits

• e137890 [string-refs] cleanup string ref code (#31443)
• d1f0472 [string-refs] remove enableLogStringRefsProd flag (#31414)
• 3dc1e48 Followup: remove dead test code from #30346 (#31415)
• 07aa494 Remove enableRefAsProp feature flag (#30346)
• 45804af [flow] Eliminate usage of more than 1-arg React.AbstractComponent in React ...
• 5636fad [string-refs] log string ref from prod (#31161)

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign leo6leo for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a openshift-knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.