fix(deps): update all non-major dependencies#5
Open
renovate[bot] wants to merge 1 commit intotrunkfrom
Open
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
6866430 to
454fb42
Compare
ada3bd2 to
f872065
Compare
35ee079 to
0b53b06
Compare
d9bced3 to
c093881
Compare
b3064c1 to
2aa2a76
Compare
573e652 to
6b75528
Compare
e1787cb to
918fd59
Compare
984b352 to
5edb73d
Compare
f79ac94 to
ab39110
Compare
|
All alerts resolved. Learn more about Socket for GitHub. This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
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.7.1→19.8.119.7.1→19.8.12.2.3→2.3.1>=0.17.1→>=0.21.7^4.1.11→^4.2.1>=2.0.12→>=2.1.10>=6.0.0→>=6.0.4>=13.5.0→>=13.9.09.31.0→9.39.39.19.0→9.39.3>=5.2.2→>=5.4.05.43.6→5.85.01.10.10→1.13.6^0.30.17→^0.30.21>=3.0.3→>=3.0.43.6.2→3.8.13.4.2→3.8.113.0.2→13.0.44.20.3→4.21.0>=7.0.8→>=7.3.1>=3.5.17→>=3.5.29>=7.3.0→>=7.4.0>=4.0.5→>=4.3.6Release Notes
conventional-changelog/commitlint (@commitlint/cli)
v19.8.1Compare Source
Bug Fixes
v19.8.0Compare Source
Performance Improvements
node:prefix to bypass require.cache call for builtins (#4302) (0cd8f41)19.7.1 (2025-02-02)
Note: Version bump only for package @commitlint/cli
19.6.1 (2024-12-15)
Note: Version bump only for package @commitlint/cli
conventional-changelog/commitlint (@commitlint/config-conventional)
v19.8.1Compare Source
Note: Version bump only for package @commitlint/config-conventional
v19.8.0Compare Source
Performance Improvements
node:prefix to bypass require.cache call for builtins (#4302) (0cd8f41)19.7.1 (2025-02-02)
Note: Version bump only for package @commitlint/config-conventional
loeffel-io/ls-lint (@ls-lint/ls-lint)
v2.3.1Compare Source
What's Changed
New Contributors
Full Changelog: loeffel-io/ls-lint@v2.3.0...v2.3.1
v2.3.0Compare Source
Please see the
v2.3.0announcement for more informations: https://ls-lint.org/blog/announcements/v2.3.0.htmlWhat's Changed
7430f06by @renovate in #21465e2c7bby @renovate in #22935c1285by @renovate in #251+= 1by @alexandear in #275New Contributors
Full Changelog: loeffel-io/ls-lint@v2.2.3...v2.3.0
posva/pinia-colada (@pinia/colada)
v0.21.7Compare Source
Bug Fixes
v0.21.6Compare Source
Bug Fixes
Performance Improvements
v0.21.5Compare Source
Bug Fixes
Features
Deprecations
The two-parameter form of
useQuery(setup, () => params)anduseQueryState(setup, () => params)is deprecated. Use a single function parameter instead:A codemod is available to automate this migration. Commit your changes first, then run:
See Migration Codemods for details.
v0.21.4Compare Source
Features
v0.21.3Compare Source
Bug Fixes
v0.21.2Compare Source
Bug Fixes
v0.21.1Compare Source
Bug Fixes
Features
v0.21.0Compare Source
Features
BREAKING CHANGES
https://pinia-colada.esm.dev/guide/installation.html#Pinia-Colada-Devtools
for instructions
v0.20.0Compare Source
This release completely changed how
useInfiniteQuery()works, the parameters and returned values:mergeoption has been removed anddatacontains an object withpagesandpageParamsarrays that can be flattened.initialPagehas now been replaced withinitialPageParamloadMorehas been renamedloadNextPagegetNextPageParamis now a required optionstalevalue higher (or disable it) to avoid refetching multiple pages when an infinite query is invalidated. Also, you might want to setrefetchOn*options tofalse.hasNextPageandhasPreviousPageAny feedback on the feature and improvements is welcome!
Here is a complete example of what it looks in action:
Bug Fixes
Features
0.19.1 (2025-12-17)
Features
v0.19.1Compare Source
Features
v0.19.0Compare Source
Bug Fixes
Features
BREAKING CHANGES
$nappended to keys for mutations and mutations without a key do not have an artificial key anymore. This is because initially the cache map was a more complex type but with it being a simple Map, there is no point in complexifying the keys. As a result themutationCache.get()now takes the id of the mutation whilegetEntries()work the same. Theexactfilter has also been removed as mutations are, by nature, meant to be called multiple times.0.18.1 (2025-12-11)
Bug Fixes
Features
0.18.0 (2025-12-02)
⚠ BREAKING CHANGES
you were relying on an external signal that aborts within the
query.It used to not set the state by just being an AbortError DomException
and now it will become an error. This behavior is more correct as we
don't want to ignore aborted signals that are external. Each fetch
creates an AbortController and passes the signal to
querywhich isaborted (without a reason) if any other method of the store fetches
again. This is done to avoid using an outdated request.
Bug Fixes
0.17.9 (2025-11-24)
Features
0.17.8 (2025-11-07)
Bug Fixes
0.17.7 (2025-10-30)
Bug Fixes
toCacheKey(#400) (d1d8f3e)Performance Improvements
0.17.6 (2025-09-25)
Bug Fixes
DefineQueryOptions(#388) (22297f0)0.17.5 (2025-09-11)
Features
0.17.4 (2025-09-09)
Bug Fixes
0.17.3 (2025-09-01)
Features
0.17.2 (2025-08-25)
Features
Bug Fixes
0.17.1 (2025-06-13)
Bug Fixes
0.17.0 (2025-06-03)
⚠ BREAKING CHANGES
EntryNodeKeywithEntryKeyEntryKeyTaggedtype now has multiple type params and an array is no longer assignable to it. This is necessary to correctly infer the types forTDataandTDataInitialand if you were manually usingEntryKeyTagged, you will either need to cast arrays to it or useEntryKeyinstead. In most cases this should not affect you. This makes types stricter and also disallows setting a query data toundefined. If you were doingqueryCache.setQueryData(key, undefined), usequeryCache.setEntryStateinstead.Features
Bug Fixes
Code Refactoring
EntryNodeKey(6c7d15b)0.16.1 (2025-05-22)
Bug Fixes
whenrelative to work across timezones (43b4f7d), closes #2930.16.0 (2025-05-21)
This is the biggest release to date! Many bug fixes, typed keys, a lighter and faster build!
⚠ BREAKING CHANGES
queryCache.invalidateQueries()now accepts a second parameter to control whether to refetch or not active queries. It can be set to'all'to force fetch all queries. This replaces the existing behavior of passingactive: null(can be removed now) which wasn't actually working. You shouldn't be negatively affected by this change as it wasn't working previously.queryCache.getEntries()). To achieve this, the hydrated version of the cache has changed.serializeTreeMaphas been removed butserializeQueryCache(which should be preferred) has been kept.EntryNodeKeyandTreeMapNode(internals) have been removed.EntryNodeKeywas juststring | number.toCacheKeyhas been adapted and now returns a plain string rather than an array. This also fixedqueryCache.getEntries(['1'])actually returning entries defined with a numeric key ([1]). The type forkeyis now stricter to ensure everything works well at the type level, you might notice it doesn't allowundefinedas a value (except in objects), this is intended as the serialized version (JSON) transforms it nonull, and will not match in the cache if used, if you want an nullish value, usenull. The documentation has been updated to reflect thisUseQueryEntryExtensionsfromTResulttoTData. Otherwise, this change won't affect you.Features
Bug Fixes
Reverts
Code Refactoring
TResultinto TData (09338a2)0.15.3 (2025-05-06)
Bug Fixes
0.15.2 (2025-05-03)
Bug Fixes
0.15.1 (2025-04-26)
Bug Fixes
0.15.0 (2025-04-18)
⚠ BREAKING CHANGES
change will only affect users directly creating entries with the mutation store
(which should be avoided except in very advanced cases). Given the new
structure of mutation entries and the fact that they are recreated for each
mutation in order to keep a history of mutations, the new process simplifies
things and reduces bundle size. The actions
createandensurein themutation store are now simpler and take less arguments (many were redundant).
Alongside these changes, the mutation store has fixed many subtle bugs.
Features
Bug Fixes
Reverts
0.14.2 (2025-03-26)
Features
Bug Fixes
0.14.1 (2025-03-18)
Bug Fixes
0.14.0 (2025-03-18)
This version introduces codemods to automate migrations 🎉. Try them out with:
You can also globally install ast-grep and run:
Remember to commit changes before running the codemods.
⚠ BREAKING CHANGES
Every global query (
useQuery()anddefineQuery())option passed to
PiniaColadahas been moved to its own optionqueryOptions:app.use(PiniaColada, { plugins: [], - gcTime: 20_000, + queryOptions: { + gcTime: 20_000, + }, })You can also use the new codemods to automatically migrate this.
types: This changes allows for Pinia Colada global options to
auto complete but it also requires you to use pass an options object to
app.use(PiniaColada, {}). This is just for typing reasons (it could bea limitation of Vue) but the same old code actually works.
Replace
serializewithserializeTreeMapRemoved
reviveTreeMap(not needed)Removed internal
createdQueryEntryFeatures
Bug Fixes
Performance Improvements
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.