chore(deps): update all non-major dependencies #113
+23
−23
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
2503cc2
to
5806fac
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
6 times, most recently
from
632a94f
to
8660093
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
3dbaed5
to
a991551
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
8 times, most recently
from
4edd72d
to
4c563d0
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
6c33f6e
to
289d36a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
c2c4890
to
e766447
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
a22472a
to
6b38e27
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
536daa2
to
7e3dc31
Compare
|
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
a711fcd
to
4cacad3
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
7 times, most recently
from
5e19f7a
to
beaa2fe
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
a3add0c
to
32cdf77
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
6 times, most recently
from
4983ca8
to
d0ae152
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
96fed4c
to
7babc1e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
7babc1e
to
c193919
Compare
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:
^4.11.0->^4.11.2^5.0.4->^5.1.0^4.0.9->^4.1.2^4.2.1->^4.4.1^8.0.1->^8.0.4^8.0.2->^8.0.5^1.3.9->^1.6.1^3.12.4->^3.14.1592^0.8.1->^0.8.4^3.12.4->^3.14.1592^3.14.0->^3.14.4^2.0.5->^2.1.5^9.9.0->^9.15.0^0.3.2->^0.4.1^4.1.3->^4.1.41->1.6.1^3.12.4->^3.14.1592^3.12.4->^3.14.15929.7.0->9.14.2^3.3.3->^3.4.0^5.5.4->^5.7.2^2.0.5->^2.1.5^2.0.29->^2.1.10Release Notes
apollographql/apollo-server (@apollo/server)
v4.11.2Compare Source
(No change; there is a change to the
@apollo/server-integration-testsuiteused to test integrations, and the two packages always have matching versions.)v4.11.1Compare Source
Patch Changes
#7952
bb81b2cThanks @glasser! - Upgrade dependencies so that automated scans don't detect a vulnerability.@apollo/serverdepends onexpresswhich depends oncookie. Versions ofexpressolder than v4.21.1 depend on a version ofcookievulnerable to CVE-2024-47764. Users of olderexpressversions who callres.cookie()orres.clearCookie()may be vulnerable to this issue.However, Apollo Server does not call this function directly, and it does not expose any object to user code that allows TypeScript users to call this function without an unsafe cast.
The only way that this direct dependency can cause a vulnerability for users of Apollo Server is if you call
startStandaloneServerwith a context function that calls Express-specific methods such asres.cookie()orres.clearCookies()on the response object, which is a violation of the TypeScript types provided bystartStandaloneServer(which only promise that the response object is a core Node.jshttp.ServerResponserather than the Express-specific subclass). So this vulnerability can only affect Apollo Server users who use unsafe JavaScript or unsafeastypecasts in TypeScript.However, this upgrade will at least prevent vulnerability scanners from alerting you to this dependency, and we encourage all Express users to upgrade their project's own
expressdependency to v4.21.1 or newer.dotansimha/graphql-code-generator (@graphql-codegen/plugin-helpers)
v5.1.0Compare Source
Minor Changes
#9989
55a1e9eThanks @eddeee888! - AddgenerateInternalResolversIfNeededoptionThis option can be used to generate more correct types for internal resolvers. For example, only generate
__resolveReferenceif the federation object has a resolvable@key.In the future, this option can be extended to support other internal resolvers e.g.
__isTypeOfis only generated for implementing types and union members.dotansimha/graphql-code-generator (@graphql-codegen/typescript)
v4.1.2Compare Source
Patch Changes
1617e3c,fa64fbf]:v4.1.1Compare Source
Patch Changes
55a1e9e,a235051]:v4.1.0Compare Source
Minor Changes
#10077
3f4f546Thanks @eddeee888! - Extendconfig.avoidOptionsto support query, mutation and subscriptionPreviously,
config.avoidOptions.resolverswas being used to make query, mutation and subscription fields non-optional.Now,
config.avoidOptions.query,config.avoidOptions.mutationandconfig.avoidOptions.subscriptioncan be used to target the respective types.Patch Changes
3f4f546]:dotansimha/graphql-code-generator (@graphql-codegen/typescript-resolvers)
v4.4.1Compare Source
Patch Changes
#10187
1617e3cThanks @gilgardosh! - Fix: type naming for imported enumsUpdated dependencies [
1617e3c,fa64fbf]:v4.4.0Compare Source
Minor Changes
#9989
55a1e9eThanks @eddeee888! - AddgenerateInternalResolversIfNeededoptionThis option can be used to generate more correct types for internal resolvers. For example, only generate
__resolveReferenceif the federation object has a resolvable@key.In the future, this option can be extended to support other internal resolvers e.g.
__isTypeOfis only generated for implementing types and union members.#10141
a235051Thanks @eddeee888! - Add avoidCheckingAbstractTypesRecursively to avoid checking and generating abstract types recursivelyFor users that already sets recursive default mappers e.g.
Partial<{T}>orDeepPartial<{T}>, having both options on will cause a nested loop which eventually crashes Codegen. In such case, settingavoidCheckingAbstractTypesRecursively: trueallows users to continue to use recursive default mappers as before.Patch Changes
55a1e9e,a235051]:v4.3.0Compare Source
Minor Changes
#10077
3f4f546Thanks @eddeee888! - Extendconfig.avoidOptionsto support query, mutation and subscriptionPreviously,
config.avoidOptions.resolverswas being used to make query, mutation and subscription fields non-optional.Now,
config.avoidOptions.query,config.avoidOptions.mutationandconfig.avoidOptions.subscriptioncan be used to target the respective types.Patch Changes
3f4f546]:ardatan/graphql-tools (@graphql-tools/graphql-file-loader)
v8.0.4Compare Source
Patch Changes
[
414e404]:v8.0.3Compare Source
Patch Changes
[
dc5043b]:v8.0.2Compare Source
Patch Changes
[
cf2ce5e]:ardatan/graphql-tools (@graphql-tools/load)
v8.0.5Compare Source
Patch Changes
[
414e404]:v8.0.4Compare Source
Patch Changes
[
dc5043b]:v8.0.3Compare Source
Patch Changes
[
cf2ce5e]:nuxt/devtools (@nuxt/devtools)
v1.6.1Compare Source
Bug Fixes
Features
v1.6.0Compare Source
Bug Fixes
1.5.2 (2024-10-02)
Bug Fixes
vite-plugin-vue-inspector(572a0d6)1.5.1 (2024-09-23)
Bug Fixes
v1.5.2Compare Source
Bug Fixes
vite-plugin-vue-inspector(572a0d6)v1.5.1Compare Source
Bug Fixes
v1.5.0Compare Source
Bug Fixes
quicktypeschema generation temporary (c1554a3)1.4.2 (2024-09-10)
Bug Fixes
1.4.1 (2024-08-26)
Bug Fixes
v1.4.2Compare Source
Bug Fixes
v1.4.1Compare Source
Bug Fixes
v1.4.0Compare Source
Features
host-clientutility (167373c)1.3.14 (2024-08-20)
1.3.13 (2024-08-20)
1.3.12 (2024-08-20)
1.3.11 (2024-08-20)
1.3.10 (2024-08-20)
Bug Fixes
Features
1.3.9 (2024-07-02)
Bug Fixes
client.revisionto trigger state editor update (418a22e)ofetchforfast-npm-meta(4188f8d)1.3.8 (2024-07-02)
Performance Improvements
npm-registry-fetch, save install size (3d74691)1.3.7 (2024-06-27)
Bug Fixes
Features
Performance Improvements
npm-registry-fetchinstead ofpacoteto deduce the package size (a049c52)1.3.6 (2024-06-21)
Features
1.3.5 (2024-06-21)
Bug Fixes
1.3.4 (2024-06-21)
Bug Fixes
1.3.3 (2024-06-04)
Bug Fixes
@vue/devtools-*(4c79fac)1.3.2 (2024-05-27)
Bug Fixes
1.3.1 (2024-05-10)
Bug Fixes
v1.3.14Compare Source
nuxt/nuxt (@nuxt/kit)
v3.14.1592Compare Source
👉 Changelog
compare changes
🩹 Fixes
webpackbarwith support for rspack (#29823)dstto deduplicate templates when adding them (#29895)dstto invalidate modules (6cd3352de)changeevents (#29954)<NuxtWelcome>when building (#29956)💅 Refactors
📖 Documentation
🏡 Chore
✅ Tests
🤖 CI
❤️ Contributors
v3.14.159Compare Source
We're leaning into the π theme - future patch releases of this minor version will just continue adding digits. (Sorry for any inconvenience! 😆)
👉 Changelog
compare changes
🩹 Fixes
module.json(#29793)mllyto resolve module paths to avoid cjs fallback (#29799)webpack-dev-middleware(#29806)📖 Documentation
🏡 Chore
❤️ Contributors
v3.14.0Compare Source
👀 Highlights
Behind the scenes, a lot has been going on in preparation for the release of Nuxt v4 (particularly on the
unjsside with preparations for Nitro v3!)⚡️ Faster starts powered by
jitiLoading the nuxt config file, as well as modules and other build-time code, is now powered by
jitiv2. You can see more about the release in the jiti v2 release notes, but one of the most important pieces is native node esm import (where possible), which should mean a faster start. ✨📂 Shared folder for code and types shared with client/server
You should never import Vue app code in your nitro code (or the other way around). But this has meant a friction point when it comes to sharing types or utilities that don't rely on the nitro/vue contexts.
For this, we have a new
shared/folder (#28682). You can't import Vue or nitro code into files in this folder, but it produces auto-imports you can consume throughout the rest of your app.If needed you can use the new
#sharedalias which points to this folder.The shared folder is alongside your
server/folder. (If you're usingcompatibilityVersion: 4, this means it's not inside yourapp/folder.)🦀
rspackbuilderWe're excited to announce a new first-class Nuxt builder for
rspack. It's still experimental but we've refactored the internal Nuxt virtual file system to useunpluginto make this possible.Let us know if you like it - and feel free to raise any issues you experience with it.
👉 To try it out, you can use this starter - or just install
@nuxt/rspack-builderand setbuilder: 'rspack'in your nuxt config file.✨ New composables
We have new
useResponseHeaderanduseRuntimeHookcomposables (#27131 and #29741).🔧 New module utilities
We now have a new
addServerTemplateutility (#29320) for adding virtual files for access inside nitro runtime routes.🚧 v4 changes
We've merged some changes which only take effect with
compatibilityVersion: 4, but which you can opt-into earlier.previously, if you had a component like
~/components/App/Header.vuethis would be visible in your devtools as<Header>. From v4 we ensure this is<AppHeader>, but it's opt-in to avoid breaking any manual<KeepAlive>you might have implemented. (#28745).Nuxt scans page metadata from your files, before calling
pages:extend. But this has led to some confusing behaviour, as pages added at this point do not end up having their page metadata respected. So we now do not scan metadata before callingpages:extend. Instead, we have a newpages:resolvedhook, which is called afterpages:extend, after all pages have been augmented with their metadata. I'd recommend opting into this by settingexperimental.scanPageMetatoafter-resolve, as it solves a number of bugs.🗺️ Roadmap to v3.15
They didn't quite make it in time for v3.14 but for the next minor release you can expect (among other things):
✅ Upgrading
As usual, our recommendation for upgrading is to run:
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
jiti(#29073)addServerTemplateutility (#29320)useResponseHeadercomposable ([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 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.
This PR was generated by Mend Renovate. View the repository job log.