Skip to content

fix(deps): update all non-major dependencies#5

Open
renovate[bot] wants to merge 1 commit intotrunkfrom
renovate/all-minor-patch
Open

fix(deps): update all non-major dependencies#5
renovate[bot] wants to merge 1 commit intotrunkfrom
renovate/all-minor-patch

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 6, 2025

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@commitlint/cli (source) 19.7.119.8.1 age confidence
@commitlint/config-conventional (source) 19.7.119.8.1 age confidence
@ls-lint/ls-lint 2.2.32.3.1 age confidence
@pinia/colada (source) >=0.17.1>=0.21.7 age confidence
@tailwindcss/oxide (source) ^4.1.11^4.2.1 age confidence
@unhead/vue (source) >=2.0.12>=2.1.10 age confidence
@vitejs/plugin-vue (source) >=6.0.0>=6.0.4 age confidence
@vueuse/core (source) >=13.5.0>=13.9.0 age confidence
eslint (source) 9.31.09.39.3 age confidence
eslint (source) 9.19.09.39.3 age confidence
fast-equals >=5.2.2>=5.4.0 age confidence
knip (source) 5.43.65.85.0 age confidence
lefthook 1.10.101.13.6 age confidence
magic-string ^0.30.17^0.30.21 age confidence
pinia (source) >=3.0.3>=3.0.4 age confidence
prettier (source) 3.6.23.8.1 age confidence
prettier (source) 3.4.23.8.1 age confidence
syncpack 13.0.213.0.4 age confidence
tsx (source) 4.20.34.21.0 age confidence
vite (source) >=7.0.8>=7.3.1 age confidence
vue (source) >=3.5.17>=3.5.29 age confidence
workbox-window (source) >=7.3.0>=7.4.0 age confidence
zod (source) >=4.0.5>=4.3.6 age confidence

Release Notes

conventional-changelog/commitlint (@​commitlint/cli)

v19.8.1

Compare Source

Bug Fixes

v19.8.0

Compare Source

Performance Improvements
  • use 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.1

Compare Source

Note: Version bump only for package @​commitlint/config-conventional

v19.8.0

Compare Source

Performance Improvements
  • use 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.1

Compare Source

What's Changed

New Contributors

Full Changelog: loeffel-io/ls-lint@v2.3.0...v2.3.1

v2.3.0

Compare Source

Please see the v2.3.0 announcement for more informations: https://ls-lint.org/blog/announcements/v2.3.0.html

What's Changed

New Contributors

Full Changelog: loeffel-io/ls-lint@v2.2.3...v2.3.0

posva/pinia-colada (@​pinia/colada)

v0.21.7

Compare Source

Bug Fixes
  • infinite: detach $onAction listener to survive component unmount (c756e3a), closes #​525

v0.21.6

Compare Source

Bug Fixes
Performance Improvements

v0.21.5

Compare Source

Bug Fixes
  • ssr: prevent memory leak (#​514) (9fd9baa)
  • types: restore UseQueryOptions variance for placeholderData callback (ef4a006)
Features
Deprecations
  • The two-parameter form of useQuery(setup, () => params) and useQueryState(setup, () => params) is deprecated. Use a single function parameter instead:

    - useQuery(useContactList, () => ({ search: search.value }))
    + useQuery(() => useContactList({ search: search.value }))

    A codemod is available to automate this migration. Commit your changes first, then run:

    pnpm --package=@​ast-grep/cli dlx ast-grep scan -r node_modules/@​pinia/colada/codemods/rules/migration-0-21-to-1-0.yaml -i src

    See Migration Codemods for details.

v0.21.4

Compare Source

Features

v0.21.3

Compare Source

Bug Fixes
  • infinite-query: compute hasNextPage correctly on cache hit (#​480) (895914a)
  • skip refetchOnWindowFocus and refetchOnReconnect for inactive defined queries (1d7f9d2), closes #​485

v0.21.2

Compare Source

Bug Fixes
  • correct GC time display for prefetched queries (#​464) (80e2c5a)
  • query: gc prefetched queries (ba1e90c)

v0.21.1

Compare Source

Bug Fixes
Features

v0.21.0

Compare Source

Features
  • expose internal utility types (bb3a7d0)
BREAKING CHANGES

v0.20.0

Compare Source

This release completely changed how useInfiniteQuery() works, the parameters and returned values:

  • The merge option has been removed and data contains an object with pages and pageParams arrays that can be flattened.
  • initialPage has now been replaced with initialPageParam
  • loadMore has been renamed loadNextPage
  • getNextPageParam is now a required option
  • Invalidating now works just as with regular queries, which means that you probably want to set stale value higher (or disable it) to avoid refetching multiple pages when an infinite query is invalidated. Also, you might want to set refetchOn* options to false.
  • It's now possible to have bi-directional navigation
  • There is now hasNextPage and hasPreviousPage

Any feedback on the feature and improvements is welcome!

Here is a complete example of what it looks in action:

<script setup lang="ts">
import { useInfiniteQuery } from '@&#8203;pinia/colada'
import { onWatcherCleanup, useTemplateRef, watch } from 'vue'

const {
  state: factsPages,
  loadNextPage,
  asyncStatus,
  isDelaying,
  hasNextPage,
} = useInfiniteQuery({
  key: ['feed'],
  query: async ({ pageParam }) => factsApi.get<CatFacts>({ query: { page: pageParam, limit: 10 } }),
  initialPageParam: 1,
  getNextPageParam(lastPage) {
    return lastPage.next_page_url
  }
  // plugins
  retry: 0,
  delay: 0,
})

// we only need an array
const facts = computed(() => factPages.value.data?.pages.flat())
const loadMoreEl = useTemplateRef('load-more')

watch(loadMoreEl, (el) => {
  if (el) {
    const observer = new IntersectionObserver(
      (entries) => {
        if (entries[0]?.isIntersecting) {
          loadNextPage()
        }
      },
      {
        rootMargin: '300px',
        threshold: [0],
      },
    )
    observer.observe(el)
    onWatcherCleanup(() => {
      observer.disconnect()
    })
  }
})
</script>

<template>
  <div>
    <button :disabled="asyncStatus === 'loading' || isDelaying" @&#8203;click="loadMore()">
      Load more (or scroll down)
    </button>
    <template v-if="facts?.length">
      <p>We have loaded {{ facts.length }} facts</p>
      <details>
        <summary>Show raw</summary>
        <pre>{{ facts }}</pre>
      </details>

      <blockquote v-for="fact in facts">
        {{ fact }}
      </blockquote>

      <p v-if="hasNextPage" ref="load-more">Loading more...</p>
    </template>
  </div>
</template>
Bug Fixes
Features

0.19.1 (2025-12-17)

Features

v0.19.1

Compare Source

Features

v0.19.0

Compare Source

Bug Fixes
  • use global options for mutations (0f3a56c)
Features
  • types: usemutationoptionswithdefaults (67ea7a6)
BREAKING CHANGES
  • Mutations id are now just an incremented number that starts at 1. There is no longer a $n appended 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 the mutationCache.get() now takes the id of the mutation while getEntries() work the same. The exact filter 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
  • While technically a fix, this is a breaking change if
    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 query which is
    aborted (without a reason) if any other method of the store fetches
    again. This is done to avoid using an outdated request.
Bug Fixes
  • query: preserve any external AbortError (0cdf7b9)

0.17.9 (2025-11-24)

Features
  • export mutation cache (892049f)
  • expose mutation cache (7f6316f)
  • warn wrong useMutationcache usage (211911d)

0.17.8 (2025-11-07)

Bug Fixes
  • allow passing extra options to defineQueryOptions (597597f)
  • types: allow interfaces in keys (19ab616), closes #​420

0.17.7 (2025-10-30)

Bug Fixes
Performance Improvements
  • avoid watched on enabled (30439c0)

0.17.6 (2025-09-25)

Bug Fixes
  • Improve type of DefineQueryOptions (#​388) (22297f0)
  • make type inference of DefineQueryOptions.placeholderData correct (#​343) (7da95dd)

0.17.5 (2025-09-11)

Features
  • query: add overloaded for optional define options params (#​386) (1c51923)

0.17.4 (2025-09-09)

Bug Fixes

0.17.3 (2025-09-01)

Features

0.17.2 (2025-08-25)

Features
  • expose internal method to plugins (740e1ce)
Bug Fixes

0.17.1 (2025-06-13)

Bug Fixes

0.17.0 (2025-06-03)

⚠ BREAKING CHANGES
  • replace EntryNodeKey with EntryKey
  • types: The EntryKeyTagged type now has multiple type params and an array is no longer assignable to it. This is necessary to correctly infer the types for TData and TDataInitial and if you were manually using EntryKeyTagged, you will either need to cast arrays to it or use EntryKey instead. In most cases this should not affect you. This makes types stricter and also disallows setting a query data to undefined. If you were doing queryCache.setQueryData(key, undefined), use queryCache.setEntryState instead.
Features
Bug Fixes
  • types: avoid incorrect undefined from tagged keys (9358619)
  • types: make options parameter optional in types (#​224) (20bca79)
Code Refactoring
  • remove deprecated EntryNodeKey (6c7d15b)

0.16.1 (2025-05-22)

Bug Fixes
  • ssr: make when relative to work across timezones (43b4f7d), closes #​293

0.16.0 (2025-05-21)

This is the biggest release to date! Many bug fixes, typed keys, a lighter and faster build!

⚠ BREAKING CHANGES
  • query: 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 passing active: 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.
  • The internal cache structure has been refactored to be simpler, faster and smaller. Keys now support deeply nested objects and partially matches them when filtering (e.g. queryCache.getEntries()). To achieve this, the hydrated version of the cache has changed. serializeTreeMap has been removed but serializeQueryCache (which should be preferred) has been kept. EntryNodeKey and TreeMapNode (internals) have been removed. EntryNodeKey was just string | number. toCacheKey has been adapted and now returns a plain string rather than an array. This also fixed queryCache.getEntries(['1']) actually returning entries defined with a numeric key ([1]). The type for key is now stricter to ensure everything works well at the type level, you might notice it doesn't allow undefined as a value (except in objects), this is intended as the serialized version (JSON) transforms it no null, and will not match in the cache if used, if you want an nullish value, use null. The documentation has been updated to reflect this
  • types: If you built a plugin, you will have to rename the type params of generics like UseQueryEntryExtensions from TResult to TData. Otherwise, this change won't affect you.
Features
  • allow deeply nested structured keys (59227a8), closes #​149
  • query: allow dynamic typed keys (0053deb)
  • query: allow for typed query keys (5068a52)
  • queryCache.setQueriesData (4818d3e)
  • types: explicit types for useInfiniteQuery (5eb9e3b)
  • types: stricter keys (02f0269)
Bug Fixes
  • avoid fetch with initialData (d1eb4c2)
  • query: gc entries created through dynamic useQuery in defineQuery (90d5d83)
  • query: invalidate inactive queries too (cf5a790), closes #​287
  • query: restore reactivity after unmounting defineQuery (dc2315a), closes #​290
  • types: make key types stricter (9669605)
Reverts
  • Revert "refactor: use external interface for QueryCache" (d6befc4)
Code Refactoring
  • types: rename TResult into TData (09338a2)

0.15.3 (2025-05-06)

Bug Fixes
  • correctly handle refetchOn* when false (262c090)

0.15.2 (2025-05-03)

Bug Fixes

0.15.1 (2025-04-26)

Bug Fixes

0.15.0 (2025-04-18)

⚠ BREAKING CHANGES
  • mutations: mutations are now created each time they are invoked. This
    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 create and ensure in the
    mutation store are now simpler and take less arguments (many were redundant).
    Alongside these changes, the mutation store has fixed many subtle bugs.
Features
  • add gcTime option for global mutations (2850167)
  • add mutation id (8c8edd5)
  • hmr: refetch on component change (56aad7a)
  • mutations: simplify the entry creation in the mutation store (a96a8ff)
  • untrack mutation entries (6b65f19)
Bug Fixes
  • an entry with no options is stale (3f59d6c)
  • defineQuery: avoid pausing still active (fe00447), closes #​246
  • mutations: create entries for each individual mutation (3def820)
  • query: avoid deleting children of gced queries (5ec6dcc)
  • setQueryData sets the status and trigger gc if possible (8137fbd)
  • types: allow tuples in keys (f8e8087)
  • types: infer initial data in setEntryState (0a94887)
Reverts
  • Revert "refactor: deprecate onMutate in favor of onBeforeMutate" (02add4a). This change never actually made it, it's here for the trace.

0.14.2 (2025-03-26)

Features
  • allow global mutation hooks (045b057)
  • avoid incompatible line with Vue 2 (0c614db)
Bug Fixes
  • defineQuery: pause the query when inactive (2b5057e), closes #​227

0.14.1 (2025-03-18)

Bug Fixes
  • types: allow extending global query options (28acdd0)

0.14.0 (2025-03-18)

This version introduces codemods to automate migrations 🎉. Try them out with:

pnpm --package=@&#8203;ast-grep/cli dlx ast-grep scan -r node_modules/@&#8203;pinia/colada/codemods/rules/migration-0-13-to-0-14.yaml -i src

You can also globally install ast-grep and run:

ast-grep scan -r node_modules/@&#8203;pinia/colada/codemods/rules/migration-0-13-to-0-14.yaml -i src

Remember to commit changes before running the codemods.

⚠ BREAKING CHANGES
  • Every global query (useQuery() and defineQuery())
    option passed to PiniaColada has been moved to its own option
    queryOptions:

    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 be
    a limitation of Vue) but the same old code actually works.

    -app.use(PiniaColada)
    +app.use(PiniaColada, {})
  • Replace serialize with serializeTreeMap

  • Removed reviveTreeMap (not needed)

  • Removed internal createdQueryEntry

Features
  • add codemods for migrations (1a2d552)
  • allow global placeholderData (a98528a), closes #​216
  • allow invalidating all queries no matter their active status (a64f674)
  • allow nullish filters (aadd11d)
Bug Fixes
  • avoid cancels to change the status (138857c), closes #​210
  • avoid unnecessary triggerCache (a3494a0)
  • initialize the infinite query pages (9efb7d4)
  • types: correctly type PiniaColada Vue plugin (f01326f)
  • types: placeholderData does not guarantee data (aed71c1), closes #​217
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.


  • If you want to rebase/retry this PR, check this box

@renovate renovate bot added the dependencies Concerns or updates related to external libraries or packages label Oct 6, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 6866430 to 454fb42 Compare October 13, 2025 09:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from ada3bd2 to f872065 Compare October 23, 2025 13:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from 35ee079 to 0b53b06 Compare October 30, 2025 14:06
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from d9bced3 to c093881 Compare November 4, 2025 21:05
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from b3064c1 to 2aa2a76 Compare November 10, 2025 02:08
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 573e652 to 6b75528 Compare December 10, 2025 05:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from e1787cb to 918fd59 Compare December 21, 2025 04:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 984b352 to 5edb73d Compare December 29, 2025 09:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from f79ac94 to ab39110 Compare January 3, 2026 00:37
@socket-security
Copy link

socket-security bot commented Jan 8, 2026

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.

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

0 participants