Update Mend: high confidence minor and patch dependency updates #2
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:
7.0.1
->7.1.1
0.26.22
->0.27.3
1.9.0
->1.12.2
1.2.1
->1.2.3
1.2.0
->1.2.1
2.2.7
->2.5.0
3.8.4
->3.11.2
3.3.5
->3.3.6
4.1.0
->4.1.1
3.5.30
->3.5.32
4.17.7
->4.17.14
5.3.14
->5.3.15
1.26.4
->1.26.5
3.0.12
->3.0.13
4.4.10
->4.4.12
6.13.5
->6.15.1
9.1.3
->9.2.1
4.23.3
->4.24.4
4.4.1
->4.4.2
3.38.0
->3.40.0
3.1.6
->3.2.3
9.0.7
->9.0.8
^0.14.0
->^0.15.0
2.29.1
->2.31.0
5.4.0
->5.5.0
6.9.0
->6.10.2
5.6.0
->5.6.3
9.0.1
->9.1.0
3.3.0
->3.3.1
5.27.0
->5.42.0
2.9.0
->2.9.2
0.5.45
->0.5.46
5.4.1
->5.5.1
3.3.3
->3.4.2
3.4.0
->3.5.0
9.1.2
->9.2.0
5.8.0
->5.9.0
17.5.1
->17.6.0
1.0.24
->1.0.25
3.4.4
->3.6.1
1.5.4
->1.5.5
5.3.10
->5.3.11
29.2.4
->29.2.5
2.6.3
->2.8.1
5.91.0
->5.97.1
5.0.4
->5.2.0
2.4.5
->2.7.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
braintree/sanitize-url (@braintree/sanitize-url)
v7.1.1
Compare Source
DevDependency Changes
Update (sub-)dependencies
v7.1.0
Compare Source
v7.0.4
Compare Source
v7.0.3
Compare Source
v7.0.2
Compare Source
floating-ui/floating-ui (@floating-ui/react)
v0.27.3
Compare Source
Patch Changes
FloatingRootContext
as thecontext
prop@floating-ui/[email protected]
v0.27.2
Compare Source
Patch Changes
inert
/aria-hidden
attributes from being left on outside elementsv0.27.1
Compare Source
Patch Changes
closeOnFocusOut
data-floating-ui-inert
whenmodal=false
v0.27.0
Compare Source
Minor Changes
inner
anduseInnerOffset
. This technique of aligning an inner element to the reference has poor performance with longer lists, doesn't fit with the middleware paradigm, doesn't work on touch, and has a better custom alternative using nativeonScroll
that is encouraged instead.| undefined
return type for React 17Patch Changes
outsideElementsInert
prop. This enables pointer modality without a backdrop.referencePress
overflow
style for scrollbar press check. Fixes an issue where outside presses would be incorrectly prevented if the target element that was pressed appeared scrollable but was actually not.v0.26.28
Compare Source
Patch Changes
useHover()
stickIfOpen
prop to determine whether to remain open upon first click when first opened by another eventreturnFocus
is ignored correctly when usingdisabled
propv0.26.27
Compare Source
Patch Changes
virtualItemRef
on floating closeroot
to be reactive fromnull
to an elementv0.26.26
Compare Source
Patch Changes
domReference
instead ofreference
v0.26.25
Compare Source
Patch Changes
restMs
enabled
optionmax-height
only if not scrollablev0.26.24
Compare Source
Patch Changes
React.JSX.Element
types. Ensure you've upgraded to the latest@types/react
patches (versions since May 6, 2023)transform
style propertymaxHeight
and applyminItemsVisible
only when scrollable@floating-ui/[email protected]
,@floating-ui/[email protected]
v0.26.23
Compare Source
Patch Changes
onOpenChange
reason string forFloatingFocusManager
'scloseOnFocusOut
handlingstaticOffset
prop if floating element is shifted. Fixes an issue where the arrow could potentially point to nothing if it was shifted enough from its reference element.onNavigate
from potentially passing in anundefined
value instead ofnull
blockPointerEvents
no longer addspointer-events: none
to unintended<body>
elements.disabled
propgrafana/faro-web-sdk (@grafana/faro-web-sdk)
v1.12.2
Compare Source
@grafana/faro-web-sdk
): Update Faro log parsing in console instrumentation to use Faro'sdefault log parser (#745)
v1.12.1
Compare Source
@grafana/faro-web-sdk
): Guard console instrumentation stringifier against circular objectreferences for non-error logs (#742)
v1.12.0
Compare Source
Fix (
@grafana/faro-web-sdk
): Guard user session stringifier against circular object references (#715)Fix (
@grafana/faro-web-sdk
): Prevents circular references in objects sent viaconsole.error
messages (#730)
Refactor (
@grafana/faro-web-sdk
): Provide config option to send log messages for console.errorcalls (#731)
Feat (
@grafana/faro-web-sdk
): Provide agetIgnoreUrls()
function to easily retrieve theconfigured ignoreUrls (#732)
v1.11.0
Compare Source
@grafana/faro-web-sdk
): The console instrumentation now sends anError
signalinstead of a
Log
signal forconsole.error()
calls (#703).@grafana/faro-web-sdk
): The resource timings instrumentation now includesttfb
(Time to First Byte) and
visibilityState
infaro.performance.resource
timings (#708).@grafana/faro-*
): Minor dependency updates.v1.10.2
Compare Source
@grafana/faro-web-tracing
): Enhance the xhr instrumentation to handle both URL objects andstrings seamlessly (#695).
v1.10.1
Compare Source
Improvement (
@grafana/faro-web-sdk
): Isolated Faro instances now exclude the default collectorURLs of other instances by default (#684).
Improvement (
@grafana/faro-web-sdk
): ThepushError
API now automatically includeserror.cause
in the Faro exception context (#688).
Fix (
@grafana/faro-transport-otlp-http [experimental]
): addservice.namespace
attribute if set(#687).
Breaking
@grafana/faro-transport-otlp-http [experimental]
): update semantic attributesfor browser (#684).
browser.user_agent
is replaced byuser_agent.original
browser.os
is replaced bybrowser.platform
v1.10.0
Compare Source
Improvement (
@grafana/faro-web-sdk
): don't automatically send aview_change
event for the defaultview (#647)
Dependencies (
@grafana/faro-web-tracing
): upgrade otel deps (#670)with it. For the web-tracing package we provide both attribute versions for now:
deployment.environment
is now deprecated and will be replaced bydeployment.environment.name
.session_id
is now deprecated and will be replaced bysession.id
Dependencies (
@grafana/faro-core
): upgrade otel deps (#670).Breaking
Dependencies (
@grafana/faro-transport-otlp-http [experimental]
): upgrade otel deps (#670)enduser.id
is replaced byuser.id
enduser.name
is replaced byuser.username
,enduser.email
is replaced byuser.email
,enduser.attributes
is replaced byuser.attributes
,http.url
is replaced byurl.full
deployment.environment
is replaced bydeployment.environment.name
v1.9.1
Compare Source
@grafana/faro-transport-otlp-http [experimental]
): Properly consume response body (#664).lezer-parser/common (@lezer/common)
v1.2.3
Compare Source
Bug fixes
Fix an issue in
TreeCursor.iterate
that made it iterate through siblings of the current node.v1.2.2
Compare Source
Bug fixes
Fix a bug in
TreeCursor.matchContext
where, if the context fell partially in a buffer node and partially in tree nodes, it could return incorrect results.lezer-parser/highlight (@lezer/highlight)
v1.2.1
Compare Source
Bug fixes
Give
Tag
objects an optional string name for debugging, and use it in theirtoString
method.reduxjs/redux-toolkit (@reduxjs/toolkit)
v2.5.0
Compare Source
This feature release updates the React peer dependency to work with React 19, and fixes an additional skip token issue.
Changelog
React 19 Compat
React 19 was just released! We've updated our peer dep to accept React 19, and updated our runtime and type tests to check against both React 18 and 19.
Also see React-Redux v9.2.0 for the same peer dep update.
Other Fixes
We previously fixed an issue with the RTKQ core where
serializeQueryArgs
callbacks could be called withskipToken
, potentially leading to errors. We've fixed an additional location in theuseQuery
hooks where that could happen as well.What's Changed
serializeQueryArgs
+skipToken
case by @markerikson in https://github.com/reduxjs/redux-toolkit/pull/4762Full Changelog: reduxjs/redux-toolkit@v2.4.0...v2.5.0
v2.4.0
Compare Source
This feature release includes multiple tweaks and fixes to RTK Query functionality, additional exported TS types, and drops support for TS versions earlier than 5.0.
Changelog
RTK Query Improvements
Lazy query hooks can now be reset.
retry.fail
now acceptsmeta
as a second argument.Tag invalidation arrays now ignore nullish values.
We did some small internal refactoring around Maps and default values that shrank bundle size slightly.
Bugfixes
Passing
skipToken
to a query hook now bails out before running any other logic, which fixes cases whereserializeQueryArgs
previously threw an error because there were no args to process.The
autoBatchEnhancer
now readswindow.requestAnimationFrame
later, which it to work properly with Jest fake timers.We fixed cases where the hook result
isSuccess
flag would briefly flicker tofalse
when switched to a different cache entry that was uninitialized, and would briefly flicker totrue
when refetching a query that previously errored.The listener middleware previously had inconsistent logic checks for comparing against existing listener entries (effect + type, vs effect only). It now always checks both effect + type.
Additional TS Types
We now export
Typed[Query|Mutation]OnQueryStarted
helpers to let you defineonQueryStarted
callbacks outside ofcreateApi
if desired.We also now export a
CreateAsyncThunkFunction
type that can be used to type userland wrappers aroundcreateAsyncThunk
.TS Support Matrix Updates
We've historically tried to maintain TS backwards compatibility as long as possible, and made occasional updates to our TS support matrix in minor versions over time. As of RTK 2.3.0, we officially supported back through TS 4.7.
As of this release, we're tweaking that support policy to match the policy used by DefinitelyTyped:
Given that, we've dropped official support for TS versions earlier than 5.0. (RTK may work with those versions, but we no longer test against them and won't try to fix issues with those versions.)
We'll continue to update our TS support matrix over time based on that 2-year rolling window.
Configuration
📅 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.