chore: update all dependencies of web #716
Closed
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:
3.7.12
->3.7.15
1.12.0
->1.12.1
11.10.5
->11.11.0
11.10.6
->11.11.1
11.10.6
->11.11.0
4.0.1
->4.1.1
7.0.7
->7.0.22
7.0.7
->7.0.22
7.0.7
->7.0.22
7.0.7
->7.0.22
7.0.7
->7.0.22
7.0.7
->7.0.22
^0.0.14-next.2
->^0.2.0
18.16.0
->18.16.18
18.0.38
->18.2.13
18.0.11
->18.2.6
4.0.0
->4.0.1
0.30.1
->0.32.2
4.24.7
->4.24.10
5.2.2
->5.3.0
8.39.0
->8.43.0
0.6.11
->0.6.12
2.2.9
->2.4.2
2.4.1
->2.4.7
21.9.2
->21.10.0
6.1.5
->6.1.8
7.7.0
->7.9.0
2.0.4
->2.2.1
21.1.1
->21.1.2
1.2.1
->1.2.2
6.10.0
->6.13.0
16.1.8
->16.1.17
7.0.7
->7.0.22
5.0.4
->5.1.3
4.3.1
->4.3.9
0.30.1
->0.32.2
Release Notes
apollographql/apollo-client
v3.7.15
Compare Source
Patch Changes
#10891
ab42a5c08
Thanks @laverdet! - Fixes a bug in how multipart responses are read when using@defer
. When reading a multipart body,HttpLink
no longer attempts to parse the boundary (e.g."---"
or other boundary string) within the response data itself, only when reading the beginning of each mulitpart chunked message.#10789
23a4e1578
Thanks @phryneas! - Fix a bug where other fields could be aliased to__typename
orid
, in which case an incoming result would be merged into the wrong cache entry.v3.7.14
Compare Source
Patch Changes
#10764
1b0a61fe5
Thanks @phryneas! - DeprecateuseFragment
returnPartialData
option#10810
a6252774f
Thanks @dleavitt! - Fix type signature ofServerError
.In <3.7
HttpLink
andBatchHttpLink
would return aServerError.message
of e.g."Unexpected token 'E', \"Error! Foo bar\" is not valid JSON"
and aServerError.result
ofundefined
in the case where a server returned a >= 300 response code with a response body containing a string that could not be parsed as JSON.In >=3.7,
message
became e.g.Response not successful: Received status code 302
andresult
became the string from the response body, however the type inServerError.result
was not updated to include thestring
type, which is now properly reflected.v3.7.13
Compare Source
Patch Changes
#10805
a5503666c
Thanks @phryneas! - Fix a potential memory leak in SSR scenarios when manypersistedQuery
instances were created over time.#10718
577c68bdd
Thanks @Hsifnus! - Delay Concast subscription teardown slightly inuseSubscription
to prevent unexpected Concast teardown when oneuseSubscription
hook tears down its in-flight Concast subscription immediately followed by anotheruseSubscription
hook reusing and subscribing to that same Concastauth0/auth0-react
v1.12.1
Compare Source
Full Changelog
Security
This patch release is identical to
1.12.0
but has been released to ensure tooling no longer detects a vulnerable version of jsonwebtoken being used by@auth0/auth0-spa-js
.Even though
1.22.5
of@auth0/auth0-spa-js
was not vulnerable for the related CVE because of the fact thatjsonwebtoken
is a devDependency of@auth0/auth0-spa-js
, we are cutting a release to ensure build tools no longer report our SDK's that use@auth0/auth0-spa-js
as vulnerable to the mentioned CVE.emotion-js/emotion
v11.11.0
Compare Source
Minor Changes
336f3d50
Thanks @Andarist! - Added support for cascade@layer
s by updating the underlying parser (stylis).Patch Changes
#3029
eed5e6cf
Thanks @Andarist! - Fixed importing in Node ESMUpdated dependencies [
336f3d50
,eed5e6cf
,336f3d50
]:v11.10.8
Compare Source
Patch Changes
#3025
6bd13425
Thanks @Andarist! - Fixed a parsing issue with&
within nested functions in declaration values by updating the underlying parser (stylis).Updated dependencies [
6bd13425
,6bd13425
]:rollup/plugins
v4.1.1
Compare Source
2023-06-19
Bugfixes
v4.1.0
Compare Source
2023-05-12
Features
storybookjs/storybook
v7.0.22
Compare Source
7.0.22
v7.0.21
Compare Source
builder-manager
adding multiple dashes to relative path - #22974, thanks @MarioCadenas!of={...}
DocBlock error in story index - #22782, thanks @shilman!v7.0.20
Compare Source
Bug Fixes
Maintenance
Build
v7.0.19
Compare Source
Bad release
v7.0.18
Compare Source
Bug Fixes
Build
v7.0.17
Compare Source
Bug Fixes
window
#22709managerHead
preset inmain.ts
#22701v7.0.16
Compare Source
Accidental no-op
v7.0.15
Compare Source
Bug Fixes
.mp3
support for builder-manager #22699v7.0.14
Compare Source
Bug Fixes
Maintenance
v7.0.13
Compare Source
Bug Fixes
global
#22393Maintenance
Build
v7.0.12
Compare Source
Bug Fixes
getFrameworkPackage
logic #22559Maintenance
v7.0.11
Compare Source
Bug Fixes
v7.0.10
Compare Source
Bug Fixes
init
#22375Maintenance
v7.0.9
Compare Source
Bug Fixes
Maintenance
v7.0.8
Compare Source
Bug Fixes
Maintenance
types
condition to the front in allpackage.json.exports
maps #22321storybookjs/testing-library
v0.2.0
Compare Source
🎉 This release contains work from a new contributor! 🎉
Thank you, Vanessa Yuen (@vanessayuenn), for all your work!
Release Notes
Upgrade user-event to v14 and testing-library to v9 (#43)
@storybook/testing-library
now uses@testing-library/dom
version 9 and@testing-library/user-event
version 14! 🎉To refer to new features and bugfixes and you can check them in the user-event release page and testing-library dom release page.
🚀 Enhancement
🐛 Bug Fix
future
npm tag tonext
#44 (@yannbf)Authors: 3
v0.1.0
Compare Source
🎉 This release contains work from a new contributor! 🎉
Thank you, Kasper Peulen (@kasperpeulen), for all your work!
🚀 Enhancement
🐛 Bug Fix
waitFor
interceptable and don't override interval/timeout #23 (@ghengeveld @yannbf)Authors: 3
vitejs/vite-plugin-react
v4.0.1
Compare Source
vitest-dev/vitest
v0.32.2
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.32.1
Compare Source
🚀 Features
registerConsoleShortcuts
fromvitest/node
- by @deot in https://github.com/vitest-dev/vitest/issues/3563 (bc49b)expect.unreachable
- by @fenghan34 and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3556 [(8e385)](https://github.com/vitest-dev/vitest/commConfiguration
📅 Schedule: Branch creation - "before 3:00 am on the 4th day of the month" (UTC), 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.
This PR has been generated by Mend Renovate. View repository job log here.