fix(deps): update mvnpm (major)#1799
Merged
Merged
Conversation
Signed-off-by: red-hat-konflux-kflux-prd-rh02 <190377777+red-hat-konflux-kflux-prd-rh02[bot]@users.noreply.github.com>
red-hat-konflux-kflux-prd-rh02
Bot
force-pushed
the
konflux/mintmaker/main/major-mvnpm
branch
from
ecb9226 to
c5dfdc1
Compare
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 contains the following updates:
5.0.0→16.0.13.0.1→8.0.17.2.1→9.0.00.0.3→6.0.01.0.6→2.1.01.22.8→2.0.0-next.616.13.1→19.2.64.5.0→5.3.22.7.0→3.3.24.0.2→5.1.114.0.0→10.0.05.2.1→6.0.12.6.9→4.4.33.3.3→4.0.27.110.1→8.55.27.110.1→10.53.17.110.1→10.53.17.110.1→10.53.17.110.1→10.53.17.110.1→10.53.1Release Notes
jsdom/whatwg-url (org.mvnpm:whatwg-url)
v16.0.1: 16.0.1Compare Source
Fixed
URL.parse()to return a properURLobject, instead of an internal implementation object. This fixes, among other things,URL.parse(x) instanceof URL.v16.0.0: 16.0.0Compare Source
Breaking change: now requires Node.js versions
^20.19.0 || ^22.12.0 || >=24.0.0.Added encoding support for query string parsing, via the new
encodingoptions toparseURL()andbasicURLParse(). (TheURLAPI is not affected, as it always uses UTF-8.) Thanks to @ChALkeR and his excellent@exodus/bytespackage for providing the foundation!v15.1.0: 15.1.0Compare Source
Updated our
tr46dependency, which updates our international domain name support to reflect Unicode 17.0.0.v15.0.0: 15.0.0Compare Source
Breaking change: now requires Node.js v20 or later.
Made minor updates to failure cases for
"host"/"hostname"and"port"state override parsing, following URL Standard changes whatwg/url@c23aec1and whatwg/url@cc8b776. These have no impact on usage of the high-level APIs.v14.2.0: 14.2.0Compare Source
Updated our
tr46dependency, which updates our international domain name support to reflect Unicode 16.0.0. Also includes the related changes to the URL Standard:cd8f1d6a6e4492c3d173f7f3e3b6Added U+005E (^) to the path percent-encode set, per whatwg/url@
9bc33c3.Ensured opaque paths always roundtrip, per whatwg/url@
6c78200.v11.0.0: 11.0.0Compare Source
The breaking changes in this release are only to the Low-level URL Standard API. No actual URL parsing or serialization behavior has changed, and users of the
URLandURLSearchParamsexports are not affected.These changes follow whatwg/url@
fbaa03c.cannotBeABaseURLproperty.pathfrom always being an array of strings, to being either a single string or an array of strings."cannot-be-a-base-URL path"parser state (i.e. value forstateOverride) to"opaque path".serializePath(urlRecord)export.hasAnOpaquePath(urlRecord)export.v9.1.0: 9.1.0Compare Source
Made the host parser reject non-IPv4 domains that end in numbers, per whatwg/url@
ab0e820.v8.7.0: 8.7.0Compare Source
Make the
pathnamesetter not mess up the URL's path state tracking when given the empty string, per whatwg/url@0672f2e.jsdom/webidl-conversions (org.mvnpm:webidl-conversions)
v8.0.1: 8.0.1Compare Source
ByteStringandUSVStringconversions. (@ChALkeR, #54)v8.0.0: 8.0.0Compare Source
Bumped Node.js version requirement to ≥20.
Removed support for environments without
SharedArrayBuffer.Removed the
allowSharedoption from theArrayBufferexport, and added a newSharedArrayBufferexport, following whatwg/webidl#1311. (@MattiasBuelens)Added the
allowResizableoption to the buffer source types andArrayBufferViewexports, following whatwg/webidl#982. (@MattiasBuelens)Fixed a bug in
SharedArrayBufferconversion. (@MattiasBuelens)v7.0.0: 7.0.0Compare Source
Bumped Node.js version requirement to ≥12.
Removed
FunctionandVoidFunctionexports. These are better handled bywebidl2js.Renamed the
voidexport toundefined, per Web IDL spec updates.Added support for environments without
SharedArrayBuffer.Fixed a typo in one of the exception messages for
BufferSource. (@ExE-Boss)v6.1.0: 6.1.0Compare Source
Fixed buffer source type conversions to throw on detached
ArrayBuffers.Fixed buffer source type conversions to throw on
SharedArrayBuffers.Added
{ allowShared: true }to buffer source type conversions, to permitSharedArrayBuffers.v5.0.0: 5.0.0Compare Source
Removed the
Errorexport, as the type was removed from Web IDL.Raised the minimum supported version to Node v8.
Fixed all buffer source type conversions to be realm-independent, i.e. they will no longer throw if given buffer source objects from other realms.
jquense/uncontrollable (org.mvnpm:uncontrollable)
v9.0.0Compare Source
Features
BREAKING CHANGES
8.0.4 (2023-07-28)
Bug Fixes
8.0.3 (2023-07-28)
Bug Fixes
8.0.2 (2023-05-22)
Bug Fixes
v8.0.4Compare Source
Bug Fixes
v8.0.3Compare Source
Bug Fixes
v8.0.2Compare Source
Bug Fixes
jsdom/tr46 (org.mvnpm:tr46)
v6.0.0: Version 6.0.0Compare Source
The minimum required Node.js version is now v20.
Updates to Unicode 17.0.0 (and thus TR 46 revision 35, whose only delta from revision 33 is the Unicode version upgrade).
v5.1.1: Version 5.1.1Compare Source
Fixes the behavior when
useSTD3ASCIIRulesis set totrue. This regressed in v5.1.0. (#70, @yandrushchak)v5.1.0: Version 5.1.0Compare Source
Updates to Unicode 16.0.0.
Updates to follow TR 46 revision 33 (spec changelog). This did not include any public API changes but did include some logic changes.
v4.1.1: Version 4.1.1Compare Source
This version fixes empty label handling, e.g. in inputs such as
xn--4-0bd15808a.which consist of one label"xn--4-0bd15808a"followed by another label"".Published specifications are ambiguous on this; TR 46 calls RFC 5893's "The Bidi Rule", which assumes all labels are nonempty. Previously,
tr46operations would fail on such inputs. Now, they behave like browsers do, and pass through the empty labels. This feedback has been given to the TR 46 authors as part of whatwg/url#744.v3.0.0: Version 3.0.0Compare Source
Raise Node.js minimum version to v12.x.
This version brings support for Unicode 14.0.0.
v2.1.0: Version 2.1.0Compare Source
This version brings support for Unicode 13.0.0.
sudodoki/toggle-selection (org.mvnpm:toggle-selection)
v2.1.0Compare Source
compare changes
🏡 Chore
v2.0.0Compare Source
🏡 Chore
index.mjsESM re-export andexports/modulefields in package.json (4cdc0d4)browserify/resolve (org.mvnpm:resolve)
v2.0.0-next.6Compare Source
v2.0.0-next.5Compare Source
v2.0.0-next.4Compare Source
v2.0.0-next.3Compare Source
v1.22.12Compare Source
v1.22.11Compare Source
v1.22.10Compare Source
v1.22.9Compare Source
facebook/react (org.mvnpm:react-is)
v19.2.6: 19.2.6 (May 6th, 2026)Compare Source
React Server Components
(#36425 by @eps1lon and @unstubbable)
v19.2.5: 19.2.5 (April 8th, 2026)Compare Source
React Server Components
v19.2.4: 19.2.4 (January 26th, 2026)Compare Source
React Server Components
v19.2.3: 19.2.3 (December 11th, 2025)Compare Source
React Server Components
v19.2.2: 19.2.2 (December 11th, 2025)Compare Source
React Server Components
react-server-dom-webpack/*.unbundledto privatereact-server-dom-unbundled(@eps1lon #35290)v19.2.1Compare Source
React Server Components
v19.2.0Compare Source
Below is a list of all new features, APIs, and bug fixes.
Read the React 19.2 release post for more information.
New React Features
<Activity>: A new API to hide and restore the UI and internal state of its children.useEffectEventis a React Hook that lets you extract non-reactive logic into an Effect Event.cacheSignal(for RSCs) lets your know when thecache()lifetime is over.New React DOM Features
resume: to resume a prerender to a stream.resumeAndPrerender: to resume a prerender to HTML.resumeToPipeableStream: to resume a prerender to a stream.resumeAndPrerenderToNodeStream: to resume a prerender to HTML.prerenderAPIs to return apostponedstate that can be passed to theresumeAPIs.Notable changes
<ViewTransition>Component. React will batch as much reveals as possible before the first paint while trying to hit popular first-contentful paint metrics.prerender,renderToReadableStream) to server-side-rendering APIs for Node.js:IDs generated by useIdAll Changes
React
<Activity />was developed over many years, starting beforeClassComponent.setState(@acdlite @sebmarkbage and many others)%oplaceholder (@eps1lon #34198)useDeferredValueloop in popstate event (@acdlite #32821)useDeferredValue(@acdlite #34376)cacheSignal(@sebmarkbage #33557)React DOM
:for IDs generated byuseId(@sebmarkbage, @eps1lon: #32001, #33342#33099, #33422)nonceto be used on hoistable styles (@Andarist #32461)React.useinsideReact.lazy-ed Component (@hi-ogawa #33941)progressiveChunkSizeoption for server-side-rendering APIs (@sebmarkbage #33027)React Server Components
<img>and<link>using hints before they're rendered (@sebmarkbage #34604)filterStackFrame(@eps1lon #33707)React Reconciler
on*handlers to account for upcoming experimental APIsv19.1.1Compare Source
React
v19.1.0Compare Source
Owner Stack
An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.
#32538, #32529, #32538
React
useIdto use valid CSS selectors, changing format from:r123:to«r123». #32001React DOM
hrefattribute is an empty string #31783getHoistableRoot()didn’t work properly when the container was a Document #32321<!-- -->) as a DOM container. #32250<script>and<template>tags to be nested within<select>tags. #31837use-sync-external-store
exportsfield topackage.jsonforuse-sync-external-storeto support various entrypoints. #25231React Server Components
unstable_prerender, a new experimental API for prerendering React Server Components on the server #31724registerServerReferencein client builds to handle server references in different environments. #32534v19.0.0Compare Source
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.
New Features
React
startTransitioncan now accept async functions. Functions passed tostartTransitionare 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 likefetch()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 formactionprop 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,useaccepts a promise or Context. If provided a promise,usewill suspend until a value is resolved.usecan only be used in render but can be called conditionally.refas a prop: Refs can now be used as props, removing the need forforwardRef.React DOM Client
<form> actionprop: Form Actions allow you to manage forms automatically and integrate withuseFormStatus. When a<form> actionsucceeds, React will automatically reset the form for uncontrolled components. The form can be reset manually with the newrequestFormResetAPI.<button> and <input> formActionprop: Actions can be passed to theformActionprop 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, andaction.<head>section of the document.<head>on the client before revealing the content of a Suspense boundary that depends on that stylesheet.preinit,preload,prefetchDNS, andpreconnectAPIs 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
prerenderandprerenderToNodeStreamAPIs for static site generation. They are designed to work with streaming environments like Node.js Streams and Web Streams. UnlikerenderToString, they wait for data to load for HTML generation.React Server Components
Deprecations
element.refaccess: React 19 supports ref as a prop, so we’re deprecatingelement.refin favor ofelement.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-nativeBreaking 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
onUncaughtErrorandonCaughtErrormethods tocreateRootandhydrateRootto customize this error handling.propTypes: UsingpropTypeswill now be silently ignored. If required, we recommend migrating to TypeScript or another type-checking solution.defaultPropsfor functions: ES6 default parameters can be used in place. Class components continue to supportdefaultPropssince there is no ES6 alternative.contextTypesandgetChildContext: Legacy Context for class components has been removed in favor of thecontextTypeAPI.React.createFactory: Now that JSX is broadly supported, allcreateFactoryusage can be migrated to JSX components.react-test-renderer/shallow: This has been a re-export of react-shallow-renderer since React 18. If needed, you can continue to use the third-party package directly. We recommend using @testing-library/react or @testing-library/react-native instead.React DOM
react-dom/test-utils: We’ve movedactfromreact-dom/test-utilsto react. All other utilities have been removed.ReactDOM.render,ReactDOM.hydrate: These have been removed in favor of the concurrent equivalents:ReactDOM.createRootandReactDOM.hydrateRoot.unmountComponentAtNode: Removed in favor ofroot.unmount().ReactDOM.findDOMNode: You can replaceReactDOM.findDOMNodewith DOM Refs.Notable Changes
React
<Context>as a provider: You can now render<Context>as a provider instead of<Context.Provider>.useDeferredValueinitial value argument: When provided,useDeferredValuewill return the initial value for the initial render of a component, then schedule a re-render in the background with thedeferredValuereturned.useMemoanduseCallbackwill now reuse the memoized results from the first render, during the second render. Additionally, StrictMode will now double-invoke ref callback functions on initial mount.React DOM
TypeScript Changes
The most common changes can be codemodded with
npx types-react-codemod@latest preset-19 ./path-to-your-react-ts-files.ReactChild(replacement:React.ReactElement | number | string)ReactFragment(replacement:Iterable<React.ReactNode>)ReactNodeArray(replacement:ReadonlyArray<React.ReactNode>)ReactText(replacement:number | string)VoidFunctionComponent(replacement:FunctionComponent)VFC(replacement:FC)prop-types:Requireable,ValidationMap,Validator,WeakValidationMapcreate-react-class:ClassicComponentClass,ClassicComponent,ClassicElement,ComponentSpec,Mixin,ReactChildren,ReactHTML,ReactSVG,SFCFactoryuseRef: The initial argument is now required to matchuseState,createContextetcuseRef()are now always mutable instead of sometimes being immutable. This feature was too confusing for users and conflicted with legit cases where refs were managed by React and manually written to.ReactElementtyping: The props of React elements now default tounknowninstead ofanyif the element is typed asReactElementJSXnamespace is removed to improve interoperability with other libraries using JSX. Instead, the JSX namespace is available from the React package:import { JSX } from 'react'useReducertypings: MostuseReducerusage should not require explicit type arguments.For example,
All Changes
React
useActionState()hook to update state based on the result of a Form Action (#27270, #27278, #27309, #27302, #27307, #27366, #27370, #27321, #27374, #27372, #27397, #27399, #27460, #28557, [#27570](https://redirect.github.com/facebook/reactConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
To execute skipped test pipelines write comment
/ok-to-test.Documentation
Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.