-
-
Notifications
You must be signed in to change notification settings - Fork 4
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 #113
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/all-minor-patch
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+22
−22
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
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
August 20, 2024 17:38
2503cc2
to
5806fac
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
6 times, most recently
from
August 29, 2024 09:54
632a94f
to
8660093
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
September 6, 2024 22:15
3dbaed5
to
a991551
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
8 times, most recently
from
September 16, 2024 01:37
4edd72d
to
4c563d0
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
September 26, 2024 00:31
6c33f6e
to
289d36a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
October 4, 2024 22:27
c2c4890
to
e766447
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
October 7, 2024 16:32
a22472a
to
6b38e27
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
October 15, 2024 15:57
536daa2
to
7e3dc31
Compare
|
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
October 20, 2024 00:14
a711fcd
to
4cacad3
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
7 times, most recently
from
November 1, 2024 23:32
5e19f7a
to
beaa2fe
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
November 6, 2024 13:52
a3add0c
to
32cdf77
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
November 13, 2024 16:58
a655b6a
to
08b849c
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
November 14, 2024 19:38
08b849c
to
5583f44
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.1
^4.2.1
->^4.4.0
^8.0.1
->^8.0.3
^8.0.2
->^8.0.4
^1.3.9
->^1.6.0
^3.12.4
->^3.14.159
^0.8.1
->^0.8.4
^3.12.4
->^3.14.159
^3.14.0
->^3.14.4
^2.0.5
->^2.1.5
^9.9.0
->^9.14.0
^0.3.2
->^0.4.1
^4.1.3
->^4.1.4
1
->1.6.1
^3.12.4
->^3.14.159
^3.12.4
->^3.14.159
9.7.0
->9.13.1
^5.5.4
->^5.6.3
^2.0.5
->^2.1.5
^2.0.29
->^2.1.10
Release Notes
apollographql/apollo-server (@apollo/server)
v4.11.2
Compare Source
(No change; there is a change to the
@apollo/server-integration-testsuite
used to test integrations, and the two packages always have matching versions.)v4.11.1
Compare Source
Patch Changes
#7952
bb81b2c
Thanks @glasser! - Upgrade dependencies so that automated scans don't detect a vulnerability.@apollo/server
depends onexpress
which depends oncookie
. Versions ofexpress
older than v4.21.1 depend on a version ofcookie
vulnerable to CVE-2024-47764. Users of olderexpress
versions 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
startStandaloneServer
with 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.ServerResponse
rather than the Express-specific subclass). So this vulnerability can only affect Apollo Server users who use unsafe JavaScript or unsafeas
typecasts 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
express
dependency to v4.21.1 or newer.dotansimha/graphql-code-generator (@graphql-codegen/plugin-helpers)
v5.1.0
Compare Source
Minor Changes
#9989
55a1e9e
Thanks @eddeee888! - AddgenerateInternalResolversIfNeeded
optionThis option can be used to generate more correct types for internal resolvers. For example, only generate
__resolveReference
if the federation object has a resolvable@key
.In the future, this option can be extended to support other internal resolvers e.g.
__isTypeOf
is only generated for implementing types and union members.dotansimha/graphql-code-generator (@graphql-codegen/typescript)
v4.1.1
Compare Source
Patch Changes
55a1e9e
,a235051
]:v4.1.0
Compare Source
Minor Changes
#10077
3f4f546
Thanks @eddeee888! - Extendconfig.avoidOptions
to support query, mutation and subscriptionPreviously,
config.avoidOptions.resolvers
was being used to make query, mutation and subscription fields non-optional.Now,
config.avoidOptions.query
,config.avoidOptions.mutation
andconfig.avoidOptions.subscription
can be used to target the respective types.Patch Changes
3f4f546
]:dotansimha/graphql-code-generator (@graphql-codegen/typescript-resolvers)
v4.4.0
Compare Source
Minor Changes
#9989
55a1e9e
Thanks @eddeee888! - AddgenerateInternalResolversIfNeeded
optionThis option can be used to generate more correct types for internal resolvers. For example, only generate
__resolveReference
if the federation object has a resolvable@key
.In the future, this option can be extended to support other internal resolvers e.g.
__isTypeOf
is only generated for implementing types and union members.#10141
a235051
Thanks @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: true
allows users to continue to use recursive default mappers as before.Patch Changes
55a1e9e
,a235051
]:v4.3.0
Compare Source
Minor Changes
#10077
3f4f546
Thanks @eddeee888! - Extendconfig.avoidOptions
to support query, mutation and subscriptionPreviously,
config.avoidOptions.resolvers
was being used to make query, mutation and subscription fields non-optional.Now,
config.avoidOptions.query
,config.avoidOptions.mutation
andconfig.avoidOptions.subscription
can be used to target the respective types.Patch Changes
3f4f546
]:ardatan/graphql-tools (@graphql-tools/graphql-file-loader)
v8.0.3
Compare Source
Patch Changes
[
dc5043b
]:v8.0.2
Compare Source
Patch Changes
[
cf2ce5e
]:ardatan/graphql-tools (@graphql-tools/load)
v8.0.4
Compare Source
Patch Changes
[
dc5043b
]:v8.0.3
Compare Source
Patch Changes
[
cf2ce5e
]:nuxt/devtools (@nuxt/devtools)
v1.6.0
Compare 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.2
Compare Source
Bug Fixes
vite-plugin-vue-inspector
(572a0d6)v1.5.1
Compare Source
Bug Fixes
v1.5.0
Compare Source
Bug Fixes
quicktype
schema generation temporary (c1554a3)1.4.2 (2024-09-10)
Bug Fixes
1.4.1 (2024-08-26)
Bug Fixes
v1.4.2
Compare Source
Bug Fixes
v1.4.1
Compare Source
Bug Fixes
v1.4.0
Compare Source
Features
host-client
utility (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.revision
to trigger state editor update (418a22e)ofetch
forfast-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-fetch
instead ofpacote
to 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.14
Compare Source
nuxt/nuxt (@nuxt/kit)
v3.14.159
Compare 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)mlly
to resolve module paths to avoid cjs fallback (#29799)webpack-dev-middleware
(#29806)📖 Documentation
🏡 Chore
❤️ Contributors
v3.14.0
Compare Source
👀 Highlights
Behind the scenes, a lot has been going on in preparation for the release of Nuxt v4 (particularly on the
unjs
side with preparations for Nitro v3!)⚡️ Faster starts powered by
jiti
Loading the nuxt config file, as well as modules and other build-time code, is now powered by
jiti
v2. 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
#shared
alias 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.)🦀
rspack
builderWe'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 useunplugin
to 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-builder
and setbuilder: 'rspack'
in your nuxt config file.✨ New composables
We have new
useResponseHeader
anduseRuntimeHook
composables (#27131 and #29741).🔧 New module utilities
We now have a new
addServerTemplate
utility (#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.vue
this 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:resolved
hook, which is called afterpages:extend
, after all pages have been augmented with their metadata. I'd recommend opting into this by settingexperimental.scanPageMeta
toafter-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)addServerTemplate
utility (#29320)useResponseHeader
composable (#27131)rspack
builder (#29142)pages:resolved
hook + scan meta post extend (#28861)definePageMeta
(#29586)shared/
folder and#shared
alias (#28682)useRuntimeHook
composable (#29741)🔥 Performance
useNuxtApp
(#29514)🩹 Fixes
InjectionType
template conditional (#29023)webpack
memfs (#29027)DOMException
as fetch abort exception (#29058)devServer.https
(#29049)buildDir
in dev mode (#29068)node_modules/
from parent urls (5bd42c893)crossorigin
attribute for stylesheets (#29138)routeRules
to hint pages to prerender (#29172)link:prefetch
(#29321)ConfigLayer
type fromc12
(#29370)typedPages
(#29352)configFile
as required in layer type (3bbcd7d21)createIsExternal
(686be8168)props
value indefinePageMeta
(#29683)nitropack/types
to ensure api routes are typed (54096875e)💅 Refactors
addBuildPlugin
internally (#29157)📖 Documentation
defineNuxtComponent
instead ofdefineComponent
(#29011)useRequestFetch
andevent.$fetch
(#29099)useFetch
errors (#29253)ofetch
headers for interceptors (#29118).env.test
(#29398)mockImplementation()
call (#29669)$fetch
(#29755)--envName
flag (#28909)📦 Build
beasties
(1b5391182)🏡 Chore
unbuild
update (71e0fb06f)jiti.import
(7ece49f9b)✅ Tests
unctx
transform (d81196122)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.