Update mvnpm - #1826
Open
red-hat-konflux-kflux-prd-rh02[bot] wants to merge 1 commit into
Open
Conversation
red-hat-konflux-kflux-prd-rh02
Bot
force-pushed
the
konflux/mintmaker/main/mvnpm
branch
6 times, most recently
from
June 24, 2026 08:08
d472994 to
7027302
Compare
red-hat-konflux-kflux-prd-rh02
Bot
force-pushed
the
konflux/mintmaker/main/mvnpm
branch
9 times, most recently
from
July 1, 2026 16:05
1bc94c1 to
6c13bc5
Compare
red-hat-konflux-kflux-prd-rh02
Bot
force-pushed
the
konflux/mintmaker/main/mvnpm
branch
5 times, most recently
from
July 10, 2026 20:05
195c759 to
1fae229
Compare
red-hat-konflux-kflux-prd-rh02
Bot
force-pushed
the
konflux/mintmaker/main/mvnpm
branch
8 times, most recently
from
July 20, 2026 08:05
3d1b357 to
6ffc05a
Compare
red-hat-konflux-kflux-prd-rh02
Bot
force-pushed
the
konflux/mintmaker/main/mvnpm
branch
from
July 22, 2026 12:05
6ffc05a to
b676a8c
Compare
red-hat-konflux-kflux-prd-rh02
Bot
force-pushed
the
konflux/mintmaker/main/mvnpm
branch
7 times, most recently
from
July 28, 2026 00:05
095e7f0 to
d15347c
Compare
red-hat-konflux-kflux-prd-rh02
Bot
force-pushed
the
konflux/mintmaker/main/mvnpm
branch
5 times, most recently
from
August 5, 2026 20:05
6515add to
df9a2e7
Compare
red-hat-konflux-kflux-prd-rh02
Bot
force-pushed
the
konflux/mintmaker/main/mvnpm
branch
4 times, most recently
from
August 14, 2026 00:05
f68c463 to
5da3120
Compare
red-hat-konflux-kflux-prd-rh02
Bot
force-pushed
the
konflux/mintmaker/main/mvnpm
branch
5 times, most recently
from
September 1, 2026 04:05
e89375e to
56a781c
Compare
red-hat-konflux-kflux-prd-rh02
Bot
force-pushed
the
konflux/mintmaker/main/mvnpm
branch
2 times, most recently
from
September 4, 2026 12:06
e089029 to
b9af8e6
Compare
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/mvnpm
branch
from
September 6, 2026 20:05
b9af8e6 to
f514db2
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
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:
19.2.7→19.2.85.6.0→5.7.05.3.2→5.3.38.5.15→8.5.285.1.11→5.1.163.49.0→3.50.04.17.24→4.17.250.4.3→0.5.110.56.0→10.73.010.56.0→10.73.010.56.0→10.73.010.56.0→10.57.01.84.0→1.84.110.56.0→10.57.0Release Notes
react/react (org.mvnpm:react-is)
v19.2.8: 19.2.8 (July 21st, 2026)Compare Source
React Server Components
(#37087 by @eps1lon)
react-icons/react-icons (org.mvnpm:react-icons)
v5.7.0Compare Source
What's Changed
Full Changelog: react-icons/react-icons@v5.6.0...v5.7.0
12920d6d006795JohannesKlauss/react-keymap-hook (org.mvnpm:react-hotkeys-hook)
v5.3.3What's Changed
New Contributors
Full Changelog: JohannesKlauss/react-hotkeys-hook@v.5.3.2...v5.3.3
postcss/postcss (org.mvnpm:postcss)
v8.5.28Compare Source
v8.5.26Compare Source
list.split()regression (by @lazerg).v8.5.25Compare Source
list.split()for non-string values (by @amir-rezaei).v8.5.24Compare Source
v8.5.23Compare Source
opts.fromfor security reasons.v8.5.22Compare Source
v8.5.21Compare Source
v8.5.20Compare Source
AtRule#paramsis set after (by @sarathfrancis90).v8.5.19Compare Source
beforefor new nodes inserted toRoot(by @MahinAnowar).v8.5.18Compare Source
opts.fromfolder for security reasons (useunsafeMap: trueto disable the check).v8.5.17Compare Source
Maximum call stack size exceedederror.postcss.fromJSON().Input#origin()for unmapped end position (by @chatman-media).v8.5.16Compare Source
Input#origin()position (by @mizdra).rawsafter rehydrating a JSON AST (by @sarathfrancis90).nodesof new node (by @MahinAnowar).offsetinpositionBy()(by @greymoth-jp).rangeBy()onindex: 0(by @sarathfrancis90).ai/nanoid (org.mvnpm:nanoid)
v5.1.16Compare Source
v5.1.15Compare Source
v5.1.14Compare Source
zloirock/core-js (org.mvnpm:core-js)
v3.50.0Compare Source
Iterator.zipIterator.zipKeyedes.namespace modules,/es/and/stable/namespace entriesIteratorchunking proposal:Iterator.prototype.chunksIterator.prototype.windowsTypeErrorinstead ofRangeErroron non-integer numberchunkSize/windowSize, following tc39/proposal-iterator-chunking/#30/actual/namespace entries, unconditional forced replacement changed to feature detectionIteratorincludes stage 3 proposal:Iterator.prototype.includesIteratorjoin stage 3 proposal:Iterator.prototype.joinPromise.allKeyedPromise.allSettledKeyedRangeErroron finite unsafe integerlimitinIterator.prototype.{ drop, take }, following tc39/ecma262/#3776PromiseResolvesemantics inPromise.try, following tc39/ecma262/#3883Iterator.prototype.flatMapbug case, #1538Object.prototype.__proto__instead of removing it, so the feature detection updatedJSON.stringifypolyfill with an array replacer - keys order now follows the replacer, inherited and non-enumerable properties are no longer ignored, #1539URL/URLSearchParamsparsing a little more correct (char sets, percent coding, etc)URL#toJSONwhenURL#toStringis reassigned after core-js is importedSymbol.forget-iterator/get-iterator-methodfixesString.prototype.{ match, search }polyfills conversion orderMAX_SAFE_INTEGERexcess check inArray.fromand{ Map, Object }.groupBypolyfillsMath.{ asinh, cbrt, log1p }polyfills with big and small valuesUint8Arraybase64 methodsescapeArray.prototype.fillonArrayBufferconstructor and%TypedArray%.prototype.fillpackage.jsonof some missed packages (just to satisfypublint)Iterator.prototype.{ drop, take }properly supported from:Promise.trymarked as not properly supported in all enginesIterator.prototype.{ chunks, windows }marked as shipped in FF154Iterator.prototype.includesmarked as shipped in FF154Iterator.prototype.includesmarked as shipped in Bun 1.4.0Iterator.prototype.joinmarked as shipped in FF154Array.prototype.includesWebKit bug marked as fixed in:queueMicrotaskBun bug marked as fixed in Bun 1.4.0stdlib-js/types (org.mvnpm.at.stdlib:types)
v0.5.1Compare Source
No changes reported for this release.
getsentry/sentry-javascript (org.mvnpm.at.sentry:types)
v10.73.0Compare Source
Important Changes
feat(v10/nextjs): Add
@sentry/nextjs/configentry point (#23766)withSentryConfigis now available from@sentry/nextjs/config, the path it moves to in v11. Importing it from@sentry/nextjsstill works on v10 but logs a warning once, so you can change yournext.configfile today and upgrade to v11 without touching it again.Other Changes
shouldHandleErroronsetupExpressErrorHandlerandsetupFasitfyErrorHandler(#23734)Internal Changes
Bundle size 📦
v10.72.0Compare Source
Important Changes
AI integrations no longer report errors that propagate to the caller (#23638, #23639, #23640)
Across all AI integrations (OpenAI, Anthropic, Google GenAI, LangChain, and LangGraph), the SDK no longer sends an event to Sentry for errors that the AI framework propagates to your code. Previously the instrumentation reported these as unhandled (
handled: false) before your own error handling ran, so an error your code caught still showed up in Sentry as an unhandled crash. The span is still marked as errored and the error still propagates, so reporting is left to your application: if your code does not handle the error, it reaches Sentry's global error handlers and is captured as unhandled, just like any other uncaught error. Errors that a provider surfaces as data on an otherwise successful response (such as Anthropic error-shaped responses or Google GenAI blocked content) are still captured, since your code never sees them propagate.feat(v10/cloudflare): Add
rpcTracePropagationBindings(#23737, #23738)The new
rpcTracePropagationBindingsoption names theenvbindings that outgoing RPC calls propagate trace context to. Strings match a binding name exactly, regular expressions match by pattern, and the default empty array propagates to nothing. RPC has no headers to carry trace context, so the SDK appends it as a trailing argument that only a Sentry-instrumented receiver removes again. List only the bindings whose receiver you know runs Sentry. Setting the option takes precedence overenableRpcTracePropagation, which is now deprecated. When you build with the Sentry Cloudflare Vite plugin, the bindings that resolve to this worker (its own Durable Objects and self service bindings) are derived from your wrangler config and added for you.Other Changes
_childSpanTimeoutID(#23673)Internal Changes
Work in this release was contributed by @ryanrho-mercor, @lux-in-tenebris-lucet, and @suhailopensource. Thank you for your contributions!
Bundle size 📦
v10.71.0Compare Source
Important Changes
The
enableLogsclient option now defaults totrue, so Sentry Logs work without any manual opt-in. Nothing is captured unless you call theSentry.logger.*APIs or add a log-forwarding integration (such asconsoleLoggingIntegration,pinoIntegration, or the winston transport), and you can setenableLogs: falseto opt out. Although a default change like this would normally land in a major release, we are shipping it in a minor after careful consideration, since it sends no data on its own and only takes effect once you actively use the logging APIs or a logging integration.Other Changes
scope.clear()method (#23231)Headersinstances (#23241)captureExceptionfrom scope, not fromClient(#23280)Internal Changes
Bundle size 📦
Configuration
📅 Schedule: (UTC)
🚦 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.