Skip to content
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

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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jun 16, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@antfu/eslint-config ^0.39.5 -> ^0.40.2 age adoption passing confidence
@nuxt/kit ^3.5.2 -> ^3.6.5 age adoption passing confidence
@nuxt/schema ^3.5.2 -> ^3.6.5 age adoption passing confidence
@nuxt/test-utils ^3.5.1 -> ^3.6.5 age adoption passing confidence
@types/node (source) ^18 -> ^18.17.5 age adoption passing confidence
@vinejs/vine ^1.4.0 -> ^1.6.0 age adoption passing confidence
changelogen ^0.5.3 -> ^0.5.4 age adoption passing confidence
eslint (source) ^8.42.0 -> ^8.47.0 age adoption passing confidence
h3 ^1.6.6 -> ^1.7.1 age adoption passing confidence
nuxt ^3.5.1 -> ^3.6.5 age adoption passing confidence
vitest ^0.31.4 -> ^0.34.1 age adoption passing confidence

Release Notes

antfu/eslint-config (@​antfu/eslint-config)

v0.40.2

Compare Source

No significant changes

    View changes on GitHub

v0.40.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.40.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.39.8

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.39.7

Compare Source

   🚀 Features
    View changes on GitHub

v0.39.6

Compare Source

   🚀 Features
    View changes on GitHub
nuxt/nuxt (@​nuxt/kit)

v3.6.5

Compare Source

3.6.5 is a hotfix patch release addressing the regression with nuxt/content introduced in v3.6.4.

v3.6.4 release notes

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

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

👉 Changelog

compare changes

🩹 Fixes
  • nuxt: Remove dist from the default ignore list (#​22227)
❤️ Contributors
  • Anthony Fu <anthonyfu117@​hotmail.com>

v3.6.4

Compare Source

3.6.4 is a patch release, brought forward to allow releasing some important bug fixes before work begins on 3.7.

Warning
We're currently investigating a regression with nuxt/content and will be releasing 3.6.5 later today.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

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

👉 Changelog

compare changes

🔥 Performance
  • nuxt,schema: Do not watch buildDir and node_modules (#​22214)
🩹 Fixes
  • nuxt: Correctly use toLowerCase for possible moduleResolution (#​22160)
  • nuxt: Don't redirect if initial path has trailing slash (#​22192)
  • nuxt: Work around payload extraction issue (#​22162)
  • nuxt: Add baseURL to island fetch requests (#​22009)
  • nuxt: Resolve race condition regenerating auto imports (#​22201)
  • nuxt: Ensure we only increment hydrating count once (#​22200)
  • nuxt: Avoid premature hydration when using async layouts (#​22198)
  • cli: Support --inspect in dev mode (#​22205)
  • test-utils: Pass along error if server can't start (#​22216)
📖 Documentation
  • Add runtime storage configuration examples (#​22189)
  • Add instruction on how to use other modules in a module (#​22081)
  • Standardize indentation and tag positioning (#​22157)
❤️ Contributors

v3.6.3

Compare Source

3.6.3 is the next patch release, including a number of fixes. It's anticipated this will be the last patch release before 3.7.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

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

👉 Changelog

compare changes

🔥 Performance
  • nuxt: Prepopulate island payloads from rendered html (#​22049)
🩹 Fixes
  • kit: Module compatibility not working with module names (6cabe69ce)
  • schema: Correct type of unctx options (4e32e70bb)
  • vite: Pass modulesDir to isExternal (#​21966)
  • nuxt: Add pages in correct hook when generating (#​22088)
  • test-utils: Export from core playwright package (#​22122)
  • nuxt: Skip view transitions where there is no route change (#​22140)
  • nuxt: Skip scanning components that do not produce a name (#​22074)
  • cli: Add aliases to monorepo paths to tsconfig includes (#​21997)
  • cli: Allow non-existent experimental option (0643d4315)
💅 Refactors
  • cli,schema: Add bundler module resolution flag (#​22142)
📖 Documentation
🏡 Chore
❤️ Contributors

v3.6.2

Compare Source

3.6.2 is the next patch release, with a raft of fixes including preparations for use without --shamefully-hoist and some fixes for data fetching within nested layouts/pages.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

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

👉 Changelog

compare changes

🔥 Performance
  • nuxt: Don't run island transform plugin if disabled (#​21844)
  • nuxt: Allow hmr for server components in dev mode (#​21916)
  • nuxt: Use getters when constructing reactive routes (#​21957)
🩹 Fixes
  • nuxt: Only redirect if path is not the same as initial url (#​21815)
  • cli: Resolve @nuxt/ui-templates from modulesDir (#​21836)
  • nuxt, vite: Do not use cjs utils to resolve/alias vue (#​21837)
  • nuxt: Improve default prerender behaviour (#​21817)
  • vite: Greater type-safety within runtime vite-node (#​21849)
  • nuxt: Ensure static presets equivalent to nuxi generate (#​21860)
  • nuxt: Handle injecting multiple entry ids for styles (#​21864)
  • nuxt: Stop loading indicator on navigation failure (#​21751)
  • cli: Respect nitro ssl cert/key variables (#​21912)
  • nuxt: Include external layers in tsconfig.json scope (#​21917)
  • nuxt: Support custom route name meta with typedPages (#​21659)
  • vite: Remove @​vue/ scoped libraries from resolutions (#​21922)
  • nuxt: Add layers in node_modules to tsconfig include (#​21929)
  • nuxt: Regenerate imports after template (#​21934)
  • vite: Fix issue detecting shadowed keyed composables (#​21891)
  • nuxt: Use $fetch.raw in dev client mode for islands (#​21904)
  • schema: Warn if user provides vite.publicDir (#​21847)
  • nuxt: Preserve old vnode when leaving nested route (#​21823)
  • kit: Ignore telemetry startup time (as it has prompt) (#​21959)
📖 Documentation
  • Add warning about dynamic import of css (#​21805)
  • Update example links (#​21811)
  • Fix broken spaLoadingTemplate link (#​21845)
  • Update useFetch return values (#​21852)
  • Describe environment override feature (#​21879)
  • Add Daniel example for hybrid rendering and Vercel (20d59d1cf)
  • Improve hybrid rendering (3fb329cc8)
  • rendering: Add end of sentence (565787183)
  • Add closing bracket (#​21887)
  • Added a note about server dynamic routes limitation (#​21919)
  • Update docs for <NuxtLoadingIndicator> (#​21952)
  • Update more links to examples repo (13a892361)
  • Add JetBrains IDEs debug configuration (#​21965)
🏡 Chore
  • Prune internal unused code and exports (#​21809)
  • Add codeflow overrides configuration (d7267663f)
✅ Tests
  • Add nuxt-vitest and composable unit tests (#​21884)
❤️ Contributors

v3.6.1

Compare Source

3.6.1 is a bugfix/patch release with some significant patches merged since 3.6.0

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

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

👉 Changelog

compare changes

🩹 Fixes
  • nuxt: Use esbuild/acorn instead of typescript dep (#​21729)
  • nuxt: Proxy headers to islands + returned prerender hints (#​21740)
  • nuxt: Respect false to disable spa loading template (#​21739)
  • nuxt: Remove path from SPA payload (#​21732)
  • nuxt: Only remove one item from middleware (#​21730)
  • nuxt: Escape colons in page paths (#​21731)
  • nuxt: Augment nitro config within server context as well (#​21724)
  • nuxt: Inline global css with ssr: false route rule (#​21763)
  • vite: Resolve css files without importer id first (#​21770)
  • vite: Emit assets referenced in inline css (#​21790)
  • nuxt: Support importing types from #imports (#​21796)
  • nuxt: Use starting index when transforming islands (#​21795)
📖 Documentation
  • Add defineNuxtRouteMiddleware migration (#​21718)
  • Add a link to Docus layer nuxt config file (#​21742)
  • Remove outdated reference to stable version (#​21785)
  • Centre example loading spinner (#​21792)
✅ Tests
❤️ Contributors

v3.6.0

Compare Source

3.6.0 is the next minor release, packed with improvements and bug fixes.

📣 Upcoming news

In the coming week you can expect two announcements:

  1. The open-sourcing of nuxt/cli by @​pi0 - a new, drop-in replacement for nuxi featuring more extensibility and better DX. We are aiming to release this alongside Nuxt 3.7, but you would be very welcome to test and contribute to nuxi-ng before then!
  2. Three significant RFCs: Nuxt Font, Nuxt Assets and Nuxt Scripts. We're expecting an initial POC to take shape in the next month, and would very much appreciate community feedback on this.

👀 Highlights

This minor release contains quite a lot, and we have big plans

 SPA loading indicator

If your site is served with ssr: false or you have disabled server-rendering on some of your pages, you might be particularly interested in the new built-in SPA loading indicator.

You can now place an HTML file in ~/app/spa-loading-template.html with some HTML you would like to use to render a loading screen that will be rendered until your app is hydrated on these pages.

👉 By default an animated Nuxt icon is rendered. You can completely disable this indicator by setting spaLoadingTemplate: false in your nuxt configuration file.

⚡️ Performance improvements

The first thing that happens when your app is hydrated is that your plugins run, and so we now perform build-time optimisations on your plugins, meaning they do not need to be normalised or reordered at runtime.

We also include your error component JS in your main entrypoint, meaning that if an error occurs when a user has no connectivity, you can still handle it with your ~/error.vue. (This also should decrease your total bundle size.)

👉 Compared to Nuxt 3.5.3, the minimal client bundle has decreased by ~0.7kB. Let's keep this up!

🔥 Fully static server components

It has been possible to use server components on static pages, but until now they would increase the payload size of your application. That is no longer true. We now store rendered server components as separate files, which are preloaded before navigation.

👉 This does rely on the new, richer JSON payload format, so make sure you have not disabled this by setting experimental.renderJsonPayloads to false.

🎨 Better style inlining

If you're monitoring your metrics closely and have not turned off experimental.inlineSSRStyles, you should see more CSS inlined in your page, and a significantly external CSS file. We're now better at deduplicating global CSS, particularly added by libraries like tailwind or unocss.

🎬 Animation controls

To give you more fine-grained control over your page/layout components, for example to create custom transitions with GSAP or other libraries, we now allow you to set pageRef on <NuxtPage> and layoutRef on <NuxtLayout. These will get passed through to the underlying DOM elements.

✨ Automatic 'static' preset detection

Up to now, running nuxt generate produced the same output on every deployment provider, but with Nuxt 3.6 we now enable static provider presets automatically. That means if you are deploying a static build (produced with nuxt generate) to a supported provider (currently vercel and netlify with cloudflare and github pages coming soon) we'll prerender your pages with special support for that provider.

This means we can configure any route rules (redirects/headers/etc) that do not require a server function. So you should get the best of both worlds when deploying a site that doesn't require runtime SSR. It also unblocks use of Nuxt Image on Vercel (with more potential for automatic provider integration coming soon).

💪 Increased type safety

We now have better support for server-specific #imports and augmentations if you are using the new ~/server/tsconfig.json we shipped in Nuxt 3.5. So when importing from #imports in your server directory, you'll get IDE auto-completion for the right import locations in Nitro, and won't see Vue auto-imports like useFetch that are unavailable within your server routes.

You should now also have type support for runtime Nitro hooks.

Finally, we have removed more locations where objects had a default any type. This should improve type safety within Nuxt in a number of locations where unspecified types fell back to any:

  • RuntimeConfig
  • PageMeta
  • NuxtApp['payload'] (accessible now from NuxtPayload interface)
  • ModuleMeta

You can find out more about how to update your code if this affects you in the original PR.

⚗️ Nitro 2.5 built-in

This release ships with new Nitro 2.5, which has a whole list of exciting improvements that are worth checking out.

Of particular note is experimental support for streaming, which is also enabled by a couple of changes in Nuxt itself.

🛠️ New tools for module authors

This release brings a number of utilities for modules authors to easily add type templates and assert compatibility with a given version of another module.

In addition, this release will finally unlock a new nuxt/module-builder mode that should improve type support for module authors. If you're a module author, you might consider following these migration steps to try it out in the coming days.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

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

👉 Changelog

compare changes

🚀 Enhancements
  • nuxt: Sync useCookie state between tabs (#​20970)
  • kit: Module compatibility utils (#​21246)
  • nuxt: Add renderResult to app:rendered (#​18610)
  • webpack: Allow configuring esbuild-loader options (#​21436)
  • nuxt: Add open option in navigateTo helper (#​21333)
  • webpack, schema: Add webpack experiments configuration (#​21446)
  • nuxt: Provide clearNuxtState composable (#​21409)
  • kit: addTypeTemplate helper with auto-registration (#​21331)
  • nuxt: Return status from useAsyncData (#​21045)
  • nuxt: Allow accessing NuxtPage ref via pageRef (#​19403)
  • nuxt: Allow accessing NuxtLayout ref via layoutRef (#​19465)
  • nuxt: Emit error in ssr-error event (#​21547)
  • nuxt: Start loading indicator state with middleware (#​21003)
  • kit: Allow direct function in defineNuxtModule (#​20763)
  • nuxt: Expose useNuxtApp to window for convenience (#​21636)
  • nuxt: Allow configuring spa loading indicator (#​21640)
  • nuxt: Add types for nuxt-defined nitro runtime hooks (#​21666)
  • nuxt: Update devdependency nitropack to v2.5.1 (#​21696)
🔥 Performance
  • nuxt: Mark define functions as side-effect free at source (#​21434)
  • nuxt: Import error component synchronously (#​21406)
  • nuxt: Use prerendered islands to serialise/revive payload (#​21461)
  • nuxt: Extract and apply plugin order at build time (#​21611)
🩹 Fixes
  • nuxt: Handle page rendering on different path (#​21408)
  • nuxt: Replace BigInt literal with BigInt constructor (#​21427)
  • vite: Remove resolveId workaround and update vite-node (#​21423)
  • schema: Remove obsolete terser option from webpack config (#​21407)
  • nuxt: Skip vue render when redirecting (#​21412)
  • nuxt: Avoid early returning renderer with empty response (#​21439)
  • nuxt: Add missing vue types (#​21445)
  • nuxt: Prefix server component ids to avoid collisions (#​21472)
  • schema: Add more explicit types for config schema (#​21475)
  • nuxt: Fix typo on nitro.autoImport option (#​21485)
  • nuxi,nuxt: Remove baseUrl + use relative paths in tsconfig (#​21081)
  • vite: Invalidate templates by dst not src (#​21501)
  • nuxt: Don't disable vue endpoint in dev mode (#​21524)
  • nuxt: Respect query/hash for external routes in navigateTo (#​21500)
  • nuxt: Abort navigation when updating window.location (#​21521)
  • vite: Ignore and warn if vite config file exists (#​21588)
  • nuxt: Ensure prerendered components are treated as islands (#​21583)
  • nuxt: Improve warning for invalid children of <Title> (#​21613)
  • nuxt: Replace : in rendered server components (for win) (#​21645)
  • cli: Add back default baseUrl in tsconfig.json (#​21632)
  • nuxt: Post non-proxied cookie value via BroadcastChannel (#​21653)
  • nuxt: Stop indicator when not changing page component (#​21656)
  • nuxt: Scroll to top in nested routes (#​21657)
  • nuxt: Inline css directly in root component (#​21573)
  • nuxt: Move to @typescript-eslint/typescript-estree (#​21664)
  • nuxt: Guard res.end() calls with check if event is handled (#​21665)
  • nuxt: Do not embed error path in payload (#​21671)
  • nuxt: Use static nitro build if possible (#​21655)
  • nuxt: Add aliases and augmentations for nitro context (#​21680)
  • nuxt,schema: Prefer unknown rather than any for signatures (#​21700)
  • schema: Change redirect type for NuxtPage type (#​21713)
  • nuxt: Fix error on layout switching (#​21450)
📖 Documentation
  • Add info about vue configuration (#​21303)
  • Include example for server utilities (#​21337)
  • Improved recommended gitignore list (#​21451)
  • Add info about merging strategy in app config (#​21462)
  • Avoid using render when defining rendering (#​21490)
  • Remove example of deprecated reactivity transform (#​21396)
  • Fix addTypeTemplate typos (#​21520)
  • Add warning about redirect check (#​20680)
  • Remove link to closed RFC (#​21564)
  • Info icon fix on "Standalone server" section (#​21589)
  • Add note to use nuxt with bridge if nitro is false (#​21586)
  • Add styling section (#​21525)
  • Add full stop (#​21614)
  • Reorder sfc blocks and add initial slash in link (#​21618)
  • Add info on extending the HTML template (#​21615)
  • Document parallel option on plugins (#​21622)
  • Americanize spelling + fix typos (#​21627)
  • Remove examples/ from repository (#​21538)
  • examples: Add bullet points (9df892a17)
  • Add experimental features page (#​21617)
  • Fix typo in experimental features (#​21663)
  • Update specified Nuxt 2 version in migration guide (#​21699)
  • Added @latest to install commands (#​21702)
🏡 Chore
  • Add vitest renovate group (7695aca93)
  • Add full version for octokit/request-action (dd5955caf)
  • Widen peer deps in renovate updates (b0ba4b864)
  • Bump bundle size 🤔 (ce4f46385)
  • Ignore webpack-dev-middleware updates on 2.x branch (7f7ae96d1)
  • Ignore vercel/netlify build directories (5d4b71426)
✅ Tests
  • Update bundle size (08df73801)
  • Skip instance error test in vite ecosystem CI (f97052cba)
🤖 CI
  • Move bundle skipping logic to workflow (#​21448)
  • Build project before calculating bundle size (ce096da96)
❤️ Contributors

v3.5.3

Compare Source

3.5.3 is expected to be the last patch release before our next raft of features lands in v3.6.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

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

👉 Changelog

compare changes

🔥 Performance
  • nuxt: Avoid watching nested paths (#​21256)
🩹 Fixes
  • nuxt: Handle serialising empty bigint (#​21257)
  • cli: Pass --no-clear config through to vite (#​21262)
  • cli: Always use the latest devtools wizard (#​21291)
  • schema: Update vue-loader options type (#​21363)
  • schema: Add types for vue experimental features (#​21364)
  • nuxt: Display errors in client overlay with typeCheck (#​21064)
  • nuxt: Support usage of std-env in runtime code (#​21372)
  • nuxt: Key distinct pages differently for legacy asyncData (#​21263)
  • vite: Skip generating keys for locally scoped functions (#​20955)
  • kit: Temporarily inline lodash.template from lodash-es (#​20892)
📖 Documentation
  • Add index.vue to page routing example (#​21240)
  • Distinguish between $fetch and fetch composables (#​21228)
  • Adjust env property to match runtimeConfig (#​21265)
  • Fix Cloudflare capitalization (#​21267)
  • Migrate transition class names and style prop (#​21281)
  • Remove irregular spaces (#​21380)
🏡 Chore
  • Pin dev dependencies (9fb83b744)
  • Avoid inlining deps in vitest (#​21316)
  • Rewrite crawler to remove old dependencies (#​21326)
  • Support vitest 0.30.0 peer dependency (d58d1ea1e)
✅ Tests
🤖 CI
  • Apply security best practices to workflows (#​21328)
  • Pin more action dependencies to hash (#​21330)
❤️ Contributors
vinejs/vine (@​vinejs/vine)

v1.6.0: Bundling with tsup

Compare Source

v1.5.3: Use validator.js specific imports

Compare Source

v1.5.2: Export VineValidator class

Compare Source

  • refactor: export VineValidator class cfaeeff
  • style: format source code 74ca7e0
  • chore: update dependencies 9b7bc07

Full Changelog: vinejs/vine@v1.5.1...v1.5.2

v1.5.1: Fix: Make schema classes Macroable to be extensible

Compare Source

  • ci: fix failing tests 2f5258c
  • ci: remove test.yml workflow file 89efc20
  • test: fix failing tests d04800c
  • test: add test for extending Vine class a417418
  • fix: make schema classes Macroable 41bd3d5

Full Changelog: vinejs/vine@v1.5.0...v1.5.1

v1.5.0: Add API to make validation metadata type-safe

Compare Source

In VineJS, you can pass runtime metadata to the validation pipeline, which you can access from the validation rules, union predicates, etc. The metadata API was not type-safe until now. However, this release allows you to define the static metadata types and a validation function to validate them at runtime.

Note: The metadata API is kept very simple because only a few schemas might need runtime metadata with a few properties to be functional.

One example is the unique validation rule. You might want the unique validation rule to check all the database rows except the one for the currently logged-in user. In that case, you will pass the currently logged-in userId to the statically compiled validation schema using metadata as follows.

const updateUserValidator = vine.compile(
  vine.object({
    email: vine.string().email().unique((field) => {
      console.log(field.meta.userId)
    }),
  })
)
await updateUserValidator.validate(data, {
  meta: { userId: request.auth.user.id }
})

However, there is no way to know that updateUserValidator needs the currently logged-in user id to be functional.

From @vinejs/[email protected], you can use the withMetaData method to define static types for the metadata a validator accepts. The schema will look as follows.

const updateUserValidator = vine
  .withMetaData<{ userId: number }>()
  .compile(
    vine.object({
      email: vine.string().email().unique((field) => {
        console.log(field.meta.userId)
      }),
    })
  )

You can pass a callback to withMetaData to validate the metadata at runtime if needed.

vine
  .withMetaData<{ userId: number }>((meta) => {
    // validate id and throw an error
 })

Commits

  • feat: add support for defining static metadata types and validator function 09c4097
  • chore: use @​adonisjs/tooling presets for tooling config a02908d
  • chore: upgrade japa to v3 4181ee4
  • chore: update dependencies f24ebb8
  • chore: add labels to exempt from stale and lock bot 92697c4
  • docs: fix contributing link fcad2fb

Full Changelog: https://github.com/vinejs/vine/


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.


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

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from deaea08 to a3aed6a Compare June 16, 2023 17:34
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 3b4bfa9 to b3bb381 Compare June 24, 2023 02:34
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from a2cd8ee to b4decbd Compare July 3, 2023 17:52
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from a0a11f0 to c734bdd Compare July 11, 2023 05:27
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 3cf4e1d to 216ddb0 Compare July 16, 2023 02:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 4f13905 to fa6d11b Compare July 26, 2023 08:42
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from ec59daa to 38747c6 Compare August 4, 2023 14:54
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 5fd447d to df20bc6 Compare August 9, 2023 08:36
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from df20bc6 to 3fcffa3 Compare August 12, 2023 05:33
@renovate renovate bot changed the title chore(deps): update all non-major dependencies chore(deps): update all non-major dependencies - autoclosed Aug 16, 2023
@renovate renovate bot closed this Aug 16, 2023
@renovate renovate bot deleted the renovate/all-minor-patch branch August 16, 2023 02:57
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