Skip to content

chore(deps): update all non-major dependencies #74

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 29, 2024

This PR contains the following updates:

Package Change Age Confidence Type Update
@biomejs/biome (source) ^2.0.4 -> ^2.0.6 age confidence devDependencies patch
@nuxt/devtools (source) ^2.2.1 -> ^2.6.2 age confidence devDependencies minor
@nuxt/kit (source) ^3.14.1592 -> ^3.17.6 age confidence dependencies minor
@nuxt/test-utils ^3.14.4 -> ^3.19.2 age confidence devDependencies minor
@types/node (source) ^22.9.1 -> ^22.16.0 age confidence devDependencies minor
bumpp ^10.0.3 -> ^10.2.0 age confidence devDependencies minor
dprint ^0.47.5 -> ^0.50.1 age confidence devDependencies minor
h3 ^1.13.0 -> ^1.15.3 age confidence devDependencies minor
lint-staged ^16.0.0 -> ^16.1.2 age confidence devDependencies minor
node (source) 22.11.0 -> 22.17.0 age confidence engines minor
pnpm (source) 9.14.2 -> 9.15.9 age confidence packageManager minor
pnpm (source) 9.14.2 -> 9.15.9 age confidence engines minor
simple-git-hooks ^2.11.1 -> ^2.13.0 age confidence devDependencies minor
taze ^19.0.0 -> ^19.1.0 age confidence devDependencies minor
typescript (source) ^5.7.2 -> ^5.8.3 age confidence devDependencies minor
vitepress (source) ^1.5.0 -> ^1.6.3 age confidence devDependencies minor
vitest (source) ^3.0.7 -> ^3.2.4 age confidence devDependencies minor

Release Notes

biomejs/biome (@​biomejs/biome)

v2.0.6

Compare Source

Patch Changes
  • #​6557 fd68458 Thanks @​ematipico! - Fixed a bug where Biome didn't provide all the available code actions when requested by the editor.

  • #​6511 72623fa Thanks @​Conaclos! - Fixed #​6492. The
    organizeImports assist action no longer duplicates a comment at the start of
    the file when :BLANK_LINE: precedes the first import group.

  • #​6557 fd68458 Thanks @​ematipico! - Fixed #​6287 where Biome Language Server didn't adhere to the settings.requireConfiguration option when pulling diagnostics and code actions.
    Note that for this configuration be correctly applied, your editor must support dynamic registration capabilities.

  • #​6551 0b63b1d Thanks @​Conaclos! - Fixed #​6536. useSortedKeys no longer panics in some edge cases where object spreads are involved.

  • #​6503 9a8fe0f Thanks @​ematipico! - Fixed #​6482 where nursery rules that belonged to a domain were incorrectly enabled.

  • #​6565 e85761c Thanks @​daivinhtran! - Fixed #​4677: Now the noUnusedImports rule won't produce diagnostics for types used in JSDoc comment of exports.

  • #​6166 b8cbd83 Thanks @​mehm8128! - Added the nursery rule noExcessiveLinesPerFunction.
    This rule restrict a maximum number of lines of code in a function body.

    The following code is now reported as invalid when the limit of maximum lines is set to 2:

    function foo() {
      const x = 0;
      const y = 1;
      const z = 2;
    }

    The following code is now reported as valid when the limit of maximum lines is set to 3:

    const bar = () => {
      const x = 0;
      const z = 2;
    };
  • #​6553 5f42630 Thanks @​denbezrukov! - Fixed #​6547. Now the Biome CSS parser correctly parses @starting-style when it's used inside other at-rules. The following example doesn't raise an error anymore:

    @​layer my-demo-layer {
      @​starting-style {
        div.showing {
          background-color: red;
        }
      }
    }
  • #​6458 05402e3 Thanks @​ematipico! - Fixed an issue where the rule useSemanticElements used the incorrect range when positioning suppression comments.

  • #​6560 6d8a6b9 Thanks @​siketyan! - Fixed #​6559: the error message on detected a large file was outdated and referred a removed configuration option files.ignore.

  • #​6458 05402e3 Thanks @​ematipico! - Fixed #​6384. The rule useAltText now emits a diagnostic with a correct range, so suppression comments can work correctly.

  • #​6518 7a56288 Thanks @​wojtekmaj! - Fixed #​6508, where the rule noUselessFragments incorrectly flagged Fragments containing HTML entities as unnecessary.

  • #​6517 c5217cf Thanks @​arendjr! - Fixed #​6515. When using the
    extends field to extend a configuration from an NPM package, we now accept the
    condition names "biome" and "default" for exporting the configuration in
    the package.json.

    This means that where previously your package.json had to contain an export
    declaration similar to this:

    {
      "exports": {
        ".": "./biome.json"
      }
    }

    You may now use one of these as well:

    {
      "exports": {
        ".": {
          "biome": "./biome.json"
        }
      }
    }

    Or:

    {
      "exports": {
        ".": {
          "default": "./biome.json"
        }
      }
    }
  • #​6219 a3a3715 Thanks @​huangtiandi1999! - Added new nursery rule noUnassignedVariables, which disallows let or var variables that are read but never assigned.

    The following code is now reported as invalid:

    let x;
    if (x) {
      console.log(1);
    }

    The following code is now reported as valid:

    let x = 1;
    if (x) {
      console.log(1);
    }
  • #​6395 f62e748 Thanks @​mdevils! - Added the new nursery rule noImplicitCoercion, which disallows shorthand type conversions in favor of explicit type conversion functions.

    Example (Invalid): Boolean conversion using double negation:

    !!foo;
    !!(foo + bar);

    Example (Invalid): Number conversion using unary operators:

    +foo;
    -(-foo);
    foo - 0;
    foo * 1;
    foo / 1;

    Example (Invalid): String conversion using concatenation:

    "" + foo;
    foo + "";
    `` + foo;
    foo += "";

    Example (Invalid): Index checking using bitwise NOT:

    ~foo.indexOf(1);
    ~foo.bar.indexOf(2);

    Example (Valid): Using explicit type conversion functions:

    Boolean(foo);
    Number(foo);
    String(foo);
    foo.indexOf(1) !== -1;
  • #​6544 f28b075 Thanks @​daivinhtran! - Fixed #​6536. Now the rule noUselessFragments produces diagnostics for a top-level useless fragment that is in a return statement.

  • #​6320 5705f1a Thanks @​mdevils! - Added the new nursery rule useUnifiedTypeSignature, which disallows overload signatures that can be unified into a single signature.

    Overload signatures that can be merged into a single signature are redundant and should be avoided. This rule helps simplify function signatures by combining overloads by making parameters optional and/or using type unions.

    Example (Invalid): Overload signatures that can be unified:

    function f(a: number): void;
    function f(a: string): void;
    interface I {
      a(): void;
      a(x: number): void;
    }

    Example (Valid): Unified signatures:

    function f(a: number | string): void {}
    interface I {
      a(x?: number): void;
    }

    Example (Valid): Different return types cannot be merged:

    interface I {
      f(): void;
      f(x: number): number;
    }
  • #​6545 2782175 Thanks @​ematipico! - Fixed #​6529, where the Biome Language Server would emit an error when the user would open a file that isn't part of its workspace (node_modules or external files).
    Now the language server doesn't emit any errors and it exits gracefully.

  • #​6524 a27b825 Thanks @​vladimir-ivanov! - Fixed #​6500: The useReadonlyClassProperties rule now correctly marks class properties as readonly when they are assigned in a constructor, setter or method,
    even if the assignment occurs inside an if or else block.

    The following code is now correctly detected by the rule:

    class Price {
      #price: string;
    
      @​Input()
      set some(value: string | number) {
        if (
          value === undefined ||
          value === null ||
          value === "undefined" ||
          value === "null" ||
          Number.isNaN(value)
        ) {
          this.#price = "";
        } else {
          this.#price = "" + value;
        }
      }
    }
  • #​6355 e128ea9 Thanks @​anthonyshew! - Added a new nursery rule noAlert that disallows the use of alert, confirm and prompt.

    The following code is deemed incorrect:

    alert("here!");
  • #​6548 37e9799 Thanks @​ematipico! - Fixed #​6459, where the Biome LSP was not taking into account the correct settings when applying source.fixAll.biome code action.

v2.0.5

Compare Source

Patch Changes
  • #​6461 38862e6 Thanks @​ematipico! - Fixed #​6419, a regression where stdin mode would create a temporary new file instead of using the one provided by the user. This was an intended regression.

    Now Biome will use the file path passed via --std-file-path, and apply the configuration that matches it.

  • #​6480 050047f Thanks @​Conaclos! - Fixed #​6371.
    useNamingConvention now checks the string case of objects' property shorthand.

  • #​6477 b98379d Thanks @​ematipico! - Fixed an issue where Biome formatter didn't format consistently CSS value separated by commas.

    .font-heading {
    - font-feature-settings: var(--heading-salt), var(--heading-ss06),
    -   var(--heading-ss11), var(--heading-cv09), var(--heading-liga),
    -   var(--heading-calt);
    
    +  font-feature-settings:
    +    var(--heading-salt), var(--heading-ss06), var(--heading-ss11),
    +    var(--heading-cv09), var(--heading-liga), var(--heading-calt);
    }
    
  • #​6248 ec7126c Thanks @​fireairforce! - Fixed grit pattern matching for different kinds of import statements.

    The grit pattern import $imports from "foo" will match the following code:

    import bar from "foo";
    import { bar } from "foo";
    import { bar, baz } from "foo";
nuxt/devtools (@​nuxt/devtools)

v2.6.2

Compare Source

Bug Fixes

v2.6.1

Compare Source

Bug Fixes

v2.6.0

Compare Source

Bug Fixes
Features

v2.5.0

Compare Source

v2.4.1

Compare Source

Bug Fixes
Features
  • improve modules view (807405f)
  • show docs link for components (9ab0ec8)

v2.4.0

Compare Source

Bug Fixes
  • devtools-kit: fix useDevtoolsClient return type (#​845) (5ce9b47)
  • module setup times are multiplied by 1000 (#​838) (d16aa96)
  • ui-kit: add [@unocss-include](https://redirect.github.com/unocss-include) magic string in NButton (#​852) (f18de78)
  • watch() typeof check on array is always false (#​850) (a873199)

2.3.2 (2025-03-26)

Bug Fixes

2.3.1 (2025-03-20)

Bug Fixes
  • downgrade execa to be compatible with Node v18, fix #​821 (f15c7dc)

v2.3.2

Compare Source

Bug Fixes

v2.3.1

Compare Source

Bug Fixes
  • downgrade execa to be compatible with Node v18, fix #​821 (f15c7dc)

v2.3.0

Compare Source

Features

2.2.1 (2025-03-05)

Bug Fixes
  • inspector: do not register instapector events if there is already any (db01e1b)
nuxt/nuxt (@​nuxt/kit)

v3.17.6

Compare Source

3.17.6 is a regularly scheduled patch release.

✅ Upgrading

Our recommendation for upgrading is to run:

npx nuxt upgrade --dedupe

This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

👉 Changelog

compare changes

🔥 Performance
  • nuxt: Decrease if checks when prerendering (#​32455)
🩹 Fixes
  • nuxt: Generate correct types for async data defaults based on nuxt.config (#​32324)
  • nuxt: Reload at base URL in nuxt:chunk-reload-immediate (#​32382)
  • nuxt: Use rollup to calculate island component filenames (#​32421)
  • nuxt: Append set-cookie headers in error handler (#​32483)
  • nuxt: Ensure asyncData runs if changing key while fetcher is running (#​32466)
  • nuxt: Handle pure hash link clicks with navigateTo (#​32393)
  • nuxt: Skip external <NuxtLink>'s custom on click handler (#​32499)
  • nuxt: Update component loader regexp for minified code (#​32298)
  • nuxt: Allow camelCase for lazy hydration attributes (#​32297)
  • nuxt: Respect inheritAttrs: false in createClientOnly fn (#​32323)
  • kit: Do not double-urlify file urls when resolving schema (#​32354)
  • nuxt: Align scroll behavior with page transition completion (#​32239)
  • nuxt: Set output.generatedCode.symbols for nitro build (#​32358)
  • nuxt: Lazily access runtimeConfig (#​32428)
💅 Refactors
  • vite: Migrate plugins internally to vite environments (#​32461)
📖 Documentation
  • Clarify where logging tag is displayed (#​32440)
  • Remove kit playground auto-import note (#​32415)
  • Remove webstorm warning (#​32513)
  • Migrate to h3js (#​32243)
  • Update the fetch clear function description (#​32287)
  • defineNuxtPlugin function documentation (#​32328)
  • Mention that <NuxtLink> encodes query params (#​32361)
  • Enhance documentation for Nuxt composables (#​32218)
  • Adjust wording to reduce confusion in lifecycle section (#​32503)
  • Improve useCookie example (367b85405)
  • Capitalise title (#​32426)
  • Mention bun.lock for lockfile (#​32427)
🏡 Chore
  • Update stackblitz reproduction link (6ab5bac66)
  • Update copilot instructions (220439055)
  • Rename deprecated vitest workspace to projects (#​32388)
  • Remove space in URL in comment (#​32394)
  • Allow setting TAG on commandline (d387e07a3)
✅ Tests
  • nuxt: Add case for key only changes with immediate: false (#​32473)
  • Separate nuxt legacy runtime tests (#​32481)
🤖 CI
❤️ Contributors

v3.17.5

Compare Source

3.17.5 is a regularly scheduled patch release.

✅ Upgrading

Our recommendation for upgrading is to run:

npx nuxt upgrade --dedupe

This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

👉 Changelog

compare changes

🔥 Performance
  • nuxt: Replace remaining instance of globby (#​31688)
🩹 Fixes
  • nuxt: Export useScriptRybbitAnalytics from script stubs (d275ae1a0)
  • nuxt: Remove unneeded pattern from regexp (2954c092c)
  • nuxt: Ensure appConfig sources are not duplicated (#​32216)
  • nuxt: Wrap slot with h() in ClientOnly (#​30664)
  • kit: Ensure template filename uses safe patterns (4372b24dd)
  • nuxt: Access asyncData state from nuxt app instance (#​32232)
  • nuxt: Make patterns relative to srcDir in buildCache (#​32260)
  • nuxt: Return non-existent route component in RouteProvider (#​32266)
  • nuxt: Use single asyncData watcher (#​32247)
  • vite: Use arrow functions in dynamic imports (#​32285)
  • webpack: Use plugin for rollup-compatible dynamic imports (#​32281)
📖 Documentation
  • Update addRouteMiddleware path in example (#​32171)
  • Narrow link to just middleware (#​32203)
  • Use optional chaining in error example (#​32214)
  • Give example of using --env-file (29f6392cd)
  • Recommend nuxt command consistently (#​32237)
  • Fix typos (#​30413)
  • Add props to special metadata (#​29708)
  • Fix wrong alert with warning in /guide/pages (#​32270)
  • Update upgrade guide + roadmap (0040ee5e7)
📦 Build
🏡 Chore
✅ Tests
  • Add regression test for useAsyncData + transition (29f7c8cb4)
  • Ensure builder tests run sequentially (defa32829)
❤️ Contributors

v3.17.4

Compare Source

3.17.4 is a regularly-scheduled patch release.

✅ Upgrading

Our recommendation for upgrading is to run:

npx nuxi@latest upgrade --dedupe

This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

👉 Changelog

compare changes

🔥 Performance
  • nuxt: Use Set for circular dep plugin (#​32110)
  • Refactor Array.includes checks to use Sets (#​32133)
  • nuxt: Use shallowRef for primitive values (#​32152)
  • nuxt: Skip route rules processing for empty child array (#​32166)
  • nuxt: Use Intl.Collator instead of localeCompare (#​32167)
🩹 Fixes
  • nuxt: Do not await lazy asyncData inside <ClientOnly> (#​32101)
  • nuxt: Respect cachedData with multiple asyncData calls (#​32099)
  • nuxt: Clear async data after a tick (#​32096)
  • nuxt: Support reactive keys in useLazyAsyncData (#​32092)
  • rspack: Use ts-checker-rspack-plugin (#​32115)
  • nuxt: Clear previous head in island-renderer (#​32100)
  • nuxt: Handle virtual files prefixed with / (#​32129)
  • schema: Remove nitro options from DeepPartial (#​31990)
  • nuxt: Ensure legacy async data remains reactive (#​32134)
  • nuxt: Pass attrs down to single child of <ClientOnly> (#​32131)
  • nuxt: Fix merge conflicts (7044450d4)
  • nuxt: Clone vnode when passing attrs down to client-only (b3acf0c78)
  • vite: Do not replace global with globalThis (#​32130)
  • nuxt: Suppress client-side errors by crawlers (#​32137)
  • nuxt: Use fresh route when <NuxtLayout> first renders (#​24673)
  • nuxt: Add additional logging when skipping error page for bot (68c270083)
  • nuxt: Add watch paths outside srcDir to parcel strategy (#​32139)
📖 Documentation
  • Use emphasis instead of quotes (#​32078)
  • Update useNuxtData default return to undefined (#​32054)
  • Capitalise headings (#​32095)
  • Prefix imports.dirs with alias (0dbf314d9)
  • Mention node v20 is minimum requirement for nuxt setup (#​32148)
  • Use more descriptive link text (d0b1b9d35)
🏡 Chore
✅ Tests
  • Add universal routing tests + clean up output (64178b6f4)
  • nuxt: Add unit tests for watch strategies (#​32138)
  • Resolve watch path (8fb562c04)
  • Use fake timers instead of setTimeout mock (#​32142)
🤖 CI
❤️ Contributors

v3.17.3

Compare Source

3.17.3 is a regularly-scheduled patch release.

✅ Upgrading

Our recommendation for upgrading is to run:

npx nuxi@latest upgrade --dedupe

This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

👉 Changelog

compare changes

🔥 Performance
  • nuxt: Pre-calculate extension glob before app resolution (#​32052)
  • nuxt: Improve islands client components chunks (#​32015)
🩹 Fixes
  • nuxt: Preload async layouts (#​32002)
  • nuxt: Handle File within FormData (#​32013)
  • schema: Respect user-provided ignore patterns (#​32020)
  • nuxt: Allow loading virtual files with query params (#​32022)
  • nuxt: Don't use reactive key for useFetch with watch: false (#​32019)
  • nuxt: Do not clear data if custom getCachedData is provided (#​32003)
  • nuxt: Provide nuxtApp for asyncData functions run on server (#​32038)
  • vite: Strip queries when skipping vite transform middleware (#​32041)
  • nuxt: Sort hash sources and files (#​32048)
  • nuxt: Do not suppress chunk import error (#​32064)
💅 Refactors
  • nuxt: Directly access initialised asyncData (e779d6cd5)
📖 Documentation
🤖 CI
  • Convert bug/enhancement labels to issue types (3ff743fe0)
  • Update payload for issue types (791e5f443)
❤️ Contributors

v3.17.2

Compare Source

3.17.2 is a regularly-scheduled patch release.

✅ Upgrading

Our recommendation for upgrading is to run:

npx nuxi@latest upgrade --dedupe

This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

👉 Changelog

compare changes

🔥 Performance
  • nuxt: Tree-shake router's handleHotUpdate in production (#​31971)
🩹 Fixes
  • nuxt: Ensure asyncData is initialised before effects run (#​31946)
  • nuxt: Skip view transition if user agent provides one before defining transition (#​31945)
  • nuxt: Improve hashing for complex body in useFetch (#​31963)
  • nuxt: Immediately call asyncData within client-only components (#​31964)
  • nuxt: Don't render errors if event is already handled (#​31966)
  • nuxt: Track whether need to reinit asyncData separately from deps (#​31965)
  • nuxt: Preserve params/meta/matched with universal router (#​31950)
  • nuxt: Respect scroll behavior set by scrollToTop (#​31914)
  • nuxt: Load live data from vfs even if a file exists in buildDir (#​31969)
  • nuxt: Short circuit middleware when validate returns false (#​31967)
  • nuxt: Ensure useAsyncData reactive to key changes when immediate: false (#​31987)
  • nuxt: Resolve real paths imported into virtual files (0bb07f129)
  • webpack: Broaden WarningFilter type (2a79dbd68)
  • schema: Broaden warningIgnoreFilters (a62e808ac)
📖 Documentation
🏡 Chore
✅ Tests
🤖 CI
  • Run docs workflow against pull requests (08f968903)
  • Run tests against node v20 (3c97d3493)
❤️ Contributors

v3.17.1

Compare Source

3.17.1 is the next patch release.

✅ Upgrading

Our recommendation for upgrading is to run:

npx nuxi@latest upgrade --dedupe

This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

👉 Changelog

compare changes

🩹 Fixes
  • nuxt: Check if match exists with new unplugin filter (#​31929)
  • nuxt: Reinitialise stale async data (#​31940)
  • nuxt: Skip view transition if user agent is providing one (#​31938)
  • nuxt: Trigger execute when non-immediate fetch key changes (#​31941)
  • nuxt: Don't redirect when route has trailing slash (#​31902)
  • ui-templates: Use escapeHTML from vue (8e4b8d62f)
  • schema: Add @vue/shared dependency (7d445c963)
📦 Build
  • Copy README/LICENSE from repo root (8e287d556)
🏡 Chore
✅ Tests
❤️ Contributors

v3.17.0

Compare Source

👀 Highlights

This release brings a major reworking of the async data layer, a new built-in component, better warnings, and performance improvements!

📊 Data Fetching Improvements

A major reorganization of Nuxt's data fetching layer brings significant improvements to useAsyncData and useFetch.

Although we have aimed to maintain backward compatibility and put breaking changes behind the experimental.granularCachedData flag (disabled by default), we recommend testing your application thoroughly after upgrading. You can also disable experimental.purgeCachedData to revert to the previous behavior if you are relying on cached data being available indefinitely after components using useAsyncData are unmounted.

👉 Read the the original PR for full details (#​31373), but here are a few highlights.

Consistent Data Across Components

All calls to useAsyncData or useFetch with the same key now share the underlying refs, ensuring consistency across your application:

<!-- ComponentA.vue -->
<script setup>
const { data: users, pending } = useAsyncData('users', fetchUsers)
</script>

<!-- ComponentB.vue -->
<script setup>
// This will reference the same data state as ComponentA
const { data: users, status } = useAsyncData('users', fetchUsers)
// When either component refreshes the data, both will update consistently
</script>

This solves various issues where components could have inconsistent data states.

Reactive Keys

You can now use computed refs, plain refs, or getter functions as keys:

const userId = ref('123')
const { data: user } = useAsyncData(
  computed(() => `user-${userId.value}`),
  () => fetchUser(userId.value)
)

// Changing the userId will automatically trigger a new data fetch
// and clean up the old data if no other components are using it
userId.value = '456'
Optimized Data Refetching

Configuration

📅 Schedule: Branch creation - "every 7 day" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from Hebilicious as a code owner November 29, 2024 01:38
Copy link

changeset-bot bot commented Nov 29, 2024

⚠️ No Changeset found

Latest commit: a4e85a9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from af31f20 to de2ea76 Compare December 5, 2024 17:18
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from b98660f to 757f439 Compare December 12, 2024 16:23
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 35fd9e2 to aa3fde9 Compare December 26, 2024 12:20
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 34a76be to 83b91fb Compare January 3, 2025 06:54
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from f2d3744 to e2b0c48 Compare January 8, 2025 23:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from 5832926 to 7ed92e7 Compare June 3, 2025 21:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 6453ab3 to ebf924a Compare June 10, 2025 03:39
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from be0197a to 4f376a7 Compare June 17, 2025 19:31
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 0bd750d to 0e50d50 Compare June 28, 2025 09:33
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 1fa437c to 70b0fb9 Compare July 2, 2025 00:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 70b0fb9 to a4e85a9 Compare July 2, 2025 02:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants