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 #2078

Merged
merged 2 commits into from Jun 9, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 24, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@docsearch/js (source) ^3.3.5 -> ^3.5.0 age adoption passing confidence
@​nuxt-themes/docus ^1.12.0 -> ^1.12.3 age adoption passing confidence
@nuxt/kit ^3.5.1 -> ^3.5.3 age adoption passing confidence
@nuxt/module-builder ^0.3.1 -> ^0.4.0 age adoption passing confidence
@nuxt/schema 3.5.1 -> 3.5.3 age adoption passing confidence
@nuxt/test-utils 3.5.1 -> 3.5.3 age adoption passing confidence
@nuxthq/studio (source) ^0.12.1 -> ^0.13.2 age adoption passing confidence
@types/ws (source) ^8.5.4 -> ^8.5.5 age adoption passing confidence
c8 ^7.13.0 -> ^7.14.0 age adoption passing confidence
eslint (source) ^8.41.0 -> ^8.42.0 age adoption passing confidence
monaco-editor-core ^0.38.0 -> ^0.39.0 age adoption passing confidence
nuxt 3.5.1 -> 3.5.3 age adoption passing confidence
pathe ^1.1.0 -> ^1.1.1 age adoption passing confidence
pnpm (source) 8.5.1 -> 8.6.1 age adoption passing confidence
release-it ^15.10.3 -> ^15.11.0 age adoption passing confidence
socket.io-client ^4.6.1 -> ^4.6.2 age adoption passing confidence
unstorage ^1.6.0 -> ^1.6.1 age adoption passing confidence
vitest ^0.31.1 -> ^0.32.0 age adoption passing confidence

Release Notes

algolia/docsearch

v3.5.0

Compare Source

Features
  • api: allow insights options to be forwarded to Autocomplete (#​1904) (26691a5)

v3.4.0

Compare Source

Features

3.3.5 (2023-05-17)

Bug Fixes

3.3.4 (2023-04-26)

Bug Fixes

3.3.3 (2023-02-06)

Bug Fixes

3.3.2 (2023-01-10)

Bug Fixes

3.3.1 (2022-12-27)

Bug Fixes
nuxt/nuxt

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

v3.5.2

Compare Source

3.5.2 is a patch release focusing on bug fixes.

✅ 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: Use .test and hoist regexps where possible (#​21011)
🩹 Fixes
  • nuxt: Fix useLazyFetch types (#​20989)
  • nuxt: Scan component dirs case-sensitively (#​20995)
  • schema: Remove duplicate @default jsdoc tag (#​21010)
  • nuxt: Add type support for router composables without pages/ integration (397c54c9d)
  • nuxt: Use simple incrementing id on client (#​20992)
  • nuxt: Treeshake <DevOnly> with webpack (#​21013)
  • nuxt: Await nuxt ready state before refreshNuxtData (#​21008)
  • nuxt: Show error page after fatal abortNavigation (#​21047)
  • nuxt: Normalize windows paths in granular watcher (#​21066)
  • nuxt: Omit Set-Cookie header if value is null (#​21072)
  • nuxt: Resolve modules relative to modulesDir (#​21082)
  • vite: Narrow vite-node inline pattern (#​21224)
📖 Documentation
🏡 Chore
✅ Tests
  • Refactor type tests into a separate fixture (#​21007)
  • Close out some missing browser contexts (3bc3aeaf6)
❤️ Contributors
nuxt/module-builder

v0.4.0

Compare Source

Features
0.3.1 (2023-05-01)
Bug Fixes
  • extend nuxt/schema as well (796d6ab)
nuxtlabs/studio.nuxt.com

v0.13.2

Compare Source

v0.13.1

Compare Source

v0.13.0

Compare Source

bcoe/c8

v7.14.0

Compare Source

Features
  • added a new CLI arg --merge-async to asynchronously and incrementally merge process coverage files to avoid OOM due to heap exhaustion (#​469) (45f2f84)
eslint/eslint

v8.42.0

Compare Source

Features

  • b8448ff feat: correct no-useless-return behaviour in try statements (#​16996) (Nitin Kumar)

Bug Fixes

  • a589636 fix: Config with ignores and without files should not always apply (#​17181) (Milos Djermanovic)
  • c4fad17 fix: Correct ignore message for "node_modules" subfolders (#​17217) (Francesco Trotta)

Documentation

  • 01d7142 docs: Update README (GitHub Actions Bot)
  • e5182b7 docs: Update README (GitHub Actions Bot)

Chores

unjs/pathe

v1.1.1

Compare Source

pnpm/pnpm

v8.6.1

Compare Source

Patch Changes

  • When dedupe-peer-dependents is enabled (default), use the path (not id) to determine compatibility.

    When multiple dependency groups can be deduplicated, the latter ones are sorted according to number of peers to allow them to benefit from deduplication.

    Resolves: #​6605

  • Some minor performance improvements by removing await from loops #​6617.

Our Gold Sponsors

Our Silver Sponsors

v8.6.0

Compare Source

Minor Changes

  • Some settings influence the structure of the lockfile, so we cannot reuse the lockfile if those settings change. As a result, we need to store such settings in the lockfile. This way we will know with which settings the lockfile has been created.

    A new field will now be present in the lockfile: settings. It will store the values of two settings: autoInstallPeers and excludeLinksFromLockfile. If someone tries to perform a frozen-lockfile installation and their active settings don't match the ones in the lockfile, then an error message will be thrown.

    The lockfile format version is bumped from v6.0 to v6.1.

    Related PR: #​6557
    Related issue: #​6312

  • A new setting, exclude-links-from-lockfile, is now supported. When enabled, specifiers of local linked dependencies won't be duplicated in the lockfile.

    This setting was primarily added for use by Bit CLI, which links core aspects to node_modules from external directories. As such, the locations may vary across different machines, resulting in the generation of lockfiles with differing locations.

Patch Changes

  • Don't print "Lockfile is up-to-date" message before finishing all the lockfile checks #​6544.
  • When updating dependencies, preserve the range prefix in aliased dependencies. So npm:foo@1.0.0 becomes npm:foo@1.1.0.
  • Print a meaningful error when a project referenced by the workspace: protocol is not found in the workspace #​4477.
  • pnpm rebuild should not fail when node-linker is set to hoisted and there are skipped optional dependencies #​6553.
  • Peers resolution should not fail when a linked in dependency resolves a peer dependency.
  • Build projects in a workspace in correct order #​6568.

Our Gold Sponsors

Our Silver Sponsors

release-it/release-it

v15.11.0

Compare Source

v15.10.5

Compare Source

v15.10.4

Compare Source

socketio/socket.io-client

v4.6.2

Compare Source

Bug Fixes
Dependencies
unjs/unstorage

v1.6.1

Compare Source

compare changes

🩹 Fixes
  • prefixStorage: Prefix getItemRaw and setItemRaw (#​232)
  • github: FetchFiles should return files (#​229)
💅 Refactors
🏡 Chore
✅ Tests
  • Skip cloudflare-kv-http on node >= 18 (33bc9c0)
❤️ Contributors
vitest-dev/vitest

v0.32.0

Compare Source

   🚨 Breaking Changes
  • Throw an error, if the module cannot be resolved  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3307 (1ad63)
    • Vitest used to fall back to the original import when it could not resolve it to the file path or the virtual module. This leads to hard-to-find module graph mismatches if you had incorrect alias or relied on relative imports to be resolved to the project root (which is usual behavior in TypeScript) because the code accidentally "worked". With this release, Vitest will now throw an error if it cannot resolve the module - there are possible edge cases that are not covered yet, so if you have any problems with this, please open a separate issue with reproduction.
  • Improve globs  -  by @​nickmccurdy in https://github.com/vitest-dev/vitest/issues/3392 (19ecc)
    • Vitest now has glob patterns similar to Jest for better compatibility. It's possible that some files will be considered test files when previously they were not. For example, Vitest now considers test.js to be a test file. Also any file in __tests__ is now considered to be a test, not just files with test or spec suffix.
  • Add @vitest/coverage-v8 package  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3339 (82112)
    • Vitest now uses v8 code coverage directly for better performance. @vitest/coverage-c8 is deprecated as Vitest no longer uses c8 package for coverage output. It will not be updated anymore, and Vitest will fail in the next version if the user has c8 as their coverage provider. Please, install the new @vitest/coverage-v8 package if you previously used @vitest/coverage-c8.
  • mocker: Don't restore mock to the original if the module is automocked  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3518 (c1004)
    • spy.mockRestore on auto-mocked named exports will no longer restore their implementation to the actual function. This behavior better matches what Jest does.
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.2

Compare Source

   🚀 Features
   🐞 Bug Fixes

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.

@netlify
Copy link

netlify bot commented May 24, 2023

Deploy Preview for nuxt-content ready!

Name Link
🔨 Latest commit
🔍 Latest deploy log https://app.netlify.com/sites/nuxt-content/deploys/64830e6458075915772e7556
😎 Deploy Preview https://deploy-preview-2078--nuxt-content.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d48934e to aa7b064 Compare May 24, 2023 22:05
@renovate renovate bot changed the title chore(deps): update dependency unstorage to ^1.6.1 chore(deps): update all non-major dependencies May 24, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 11 times, most recently from 6935ba4 to 293a45f Compare June 2, 2023 13:34
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from b14d47f to bbd7f92 Compare June 8, 2023 17:59
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from bbd7f92 to 6818cc1 Compare June 8, 2023 22:56
@renovate
Copy link
Contributor Author

renovate bot commented Jun 9, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@farnabaz farnabaz merged commit 63f8aaa into main Jun 9, 2023
7 checks passed
@farnabaz farnabaz deleted the renovate/all-minor-patch branch June 9, 2023 11:42
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.

None yet

1 participant