fix(deps): update all dependencies - patch updates #260
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.19.1
->4.19.13
0.5.0
->0.5.1
5.0.2
->5.0.5
10.0.13
->10.0.23
0.25.0
->0.25.2
5.2.1
->5.2.6
11.0.0
->11.0.1
1.22.1
->1.22.4
3.3.0
->3.3.1
6.21.1
->6.21.2
8.18.0
->8.18.1
3.24.1
->3.24.2
Release Notes
apollographql/apollo-client-devtools (@apollo/client-devtools-vscode)
v4.19.13
Compare Source
Patch Changes
05e063b
Thanks @github-actions! - add error codes for new Apollo Client versionv4.19.12
Compare Source
Patch Changes
205ca9d
Thanks @github-actions! - add error codes for new Apollo Client versionv4.19.11
Compare Source
Patch Changes
6e352d8
Thanks @github-actions! - add error codes for new Apollo Client versionv4.19.10
Compare Source
Patch Changes
2f1068f
Thanks @github-actions! - add error codes for new Apollo Client versionv4.19.9
Compare Source
Patch Changes
7cdba68
Thanks @github-actions! - add error codes for new Apollo Client versionv4.19.8
Compare Source
Patch Changes
1152790
Thanks @github-actions! - add error codes for new Apollo Client versionv4.19.7
Compare Source
Patch Changes
891821c
Thanks @github-actions! - add error codes for new Apollo Client versionv4.19.6
Compare Source
v4.19.5
Compare Source
v4.19.4
Compare Source
v4.19.3
Compare Source
v4.19.2
Compare Source
changesets/changesets (@changesets/changelog-github)
v0.5.1
Compare Source
Patch Changes
84a4a1b
]:dotansimha/graphql-code-generator (@graphql-codegen/cli)
v5.0.5
Compare Source
Patch Changes
7d7760d
Thanks @oprypkhantc! - Fix watcher watching project root when schema URL is usedv5.0.4
Compare Source
Patch Changes
#10248
72eb86f
Thanks @renovate! - dependencies updates:@whatwg-node/fetch@^0.10.0
↗︎ (from^0.9.20
, independencies
)#10227
6f1741a
Thanks @eddeee888! - Fix schema pointers type to allow an array of pointersUpdated dependencies [
8737dd8
,ed71811
]:v5.0.3
Compare Source
Patch Changes
#10069
8bb34e7
Thanks @renovate! - dependencies updates:@whatwg-node/fetch@^0.9.20
↗︎ (from^0.8.0
, independencies
)graphql-config@^5.1.1
↗︎ (from^5.0.2
, independencies
)e0092b5
Thanks @ardatan! - Bump whatwg-node and graphql-configUpdated dependencies [
8471a18
,67e7556
]:ardatan/graphql-tools (@graphql-tools/schema)
v10.0.23
Compare Source
Patch Changes
[
d123e26
]:v10.0.22
Compare Source
Patch Changes
[
4899c62
,90a717e
,26518de
]:v10.0.21
Compare Source
Patch Changes
[
155944b
]:v10.0.20
Compare Source
Patch Changes
[
4a2eb14
]:v10.0.19
Compare Source
Patch Changes
[
3547bba
]:v10.0.18
Compare Source
Patch Changes
[
651a5dc
]:v10.0.17
Compare Source
Patch Changes
357b2ee
Thanks @renovate! - dependencies updates:
value-or-promise@^1.0.12
↗︎ (fromdependencies
)[
0a3e193
,357b2ee
]:v10.0.16
Compare Source
Patch Changes
[
53bb601
,53bb601
]:v10.0.15
Compare Source
Patch Changes
[
4912f19
]:v10.0.14
Compare Source
Patch Changes
[
2c70d27
]:evanw/esbuild (esbuild)
v0.25.2
Compare Source
Support flags in regular expressions for the API (#4121)
The JavaScript plugin API for esbuild takes JavaScript regular expression objects for the
filter
option. Internally these are translated into Go regular expressions. However, this translation previously ignored theflags
property of the regular expression. With this release, esbuild will now translate JavaScript regular expression flags into Go regular expression flags. Specifically the JavaScript regular expression/\.[jt]sx?$/i
is turned into the Go regular expression`(?i)\.[jt]sx?$`
internally inside of esbuild's API. This should make it possible to use JavaScript regular expressions with thei
flag. Note that JavaScript and Go don't support all of the same regular expression features, so this mapping is only approximate.Fix node-specific annotations for string literal export names (#4100)
When node instantiates a CommonJS module, it scans the AST to look for names to expose via ESM named exports. This is a heuristic that looks for certain patterns such as
exports.NAME = ...
ormodule.exports = { ... }
. This behavior is used by esbuild to "annotate" CommonJS code that was converted from ESM with the original ESM export names. For example, when converting the fileexport let foo, bar
from ESM to CommonJS, esbuild appends this to the end of the file:However, this feature previously didn't work correctly for export names that are not valid identifiers, which can be constructed using string literal export names. The generated code contained a syntax error. That problem is fixed in this release:
Basic support for index source maps (#3439, #4109)
The source map specification has an optional mode called index source maps that makes it easier for tools to create an aggregate JavaScript file by concatenating many smaller JavaScript files with source maps, and then generate an aggregate source map by simply providing the original source maps along with some offset information. My understanding is that this is rarely used in practice. I'm only aware of two uses of it in the wild: ClojureScript and Turbopack.
This release provides basic support for indexed source maps. However, the implementation has not been tested on a real app (just on very simple test input). If you are using index source maps in a real app, please try this out and report back if anything isn't working for you.
Note that this is also not a complete implementation. For example, index source maps technically allows nesting source maps to an arbitrary depth, while esbuild's implementation in this release only supports a single level of nesting. It's unclear whether supporting more than one level of nesting is important or not given the lack of available test cases.
This feature was contributed by @clyfish.
v0.25.1
Compare Source
Fix incorrect paths in inline source maps (#4070, #4075, #4105)
This fixes a regression from version 0.25.0 where esbuild didn't correctly resolve relative paths contained within source maps in inline
sourceMappingURL
data URLs. The paths were incorrectly being passed through as-is instead of being resolved relative to the source file containing thesourceMappingURL
comment, which was due to the data URL not being a file URL. This regression has been fixed, and this case now has test coverage.Fix invalid generated source maps (#4080, #4082, #4104, #4107)
This release fixes a regression from version 0.24.1 that could cause esbuild to generate invalid source maps. Specifically under certain conditions, esbuild could generate a mapping with an out-of-bounds source index. It was introduced by code that attempted to improve esbuild's handling of "null" entries in source maps (i.e. mappings with a generated position but no original position). This regression has been fixed.
This fix was contributed by @jridgewell.
Fix a regression with non-file source map paths (#4078)
The format of paths in source maps that aren't in the
file
namespace was unintentionally changed in version 0.25.0. Path namespaces is an esbuild-specific concept that is optionally available for plugins to use to distinguish paths fromfile
paths and from paths meant for other plugins. Previously the namespace was prepended to the path joined with a:
character, but version 0.25.0 unintentionally failed to prepend the namespace. The previous behavior has been restored.Fix a crash with
switch
optimization (#4088)The new code in the previous release to optimize dead code in switch statements accidentally introduced a crash in the edge case where one or more switch case values include a function expression. This is because esbuild now visits the case values first to determine whether any cases are dead code, and then visits the case bodies once the dead code status is known. That triggered some internal asserts that guard against traversing the AST in an unexpected order. This crash has been fixed by changing esbuild to expect the new traversal ordering. Here's an example of affected code:
Update Go from 1.23.5 to 1.23.7 (#4076, #4077)
This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain reports from vulnerability scanners that detect which version of the Go compiler esbuild uses.
This PR was contributed by @MikeWillCook.
prettier/eslint-plugin-prettier (eslint-plugin-prettier)
v5.2.6
Compare Source
Patch Changes
1451176
Thanks @renovate! - fix(deps): bumpsynckit
tov0.11.0
v5.2.5
Compare Source
Patch Changes
4f5513d
Thanks @JounQin! - fix: clarify correcteslint-config-prettier
peer rangev5.2.4
Compare Source
Patch Changes
b8cfe56
Thanks @JounQin! - chore: hourcekeeping, bump all (dev) depsv5.2.3
Compare Source
Patch Changes
9c6141f
Thanks @BPScott! - Add name field to recommended flat configv5.2.2
Compare Source
Patch Changes
aa5b59f
Thanks @ntnyq! - fix: report node when loc not foundisaacs/node-glob (glob)
v11.0.1
Compare Source
graphql/graphql-http (graphql-http)
v1.22.4
Compare Source
Bug Fixes
v1.22.3
Compare Source
Bug Fixes
status
andstatusText
are optional (38a0191), closes #133v1.22.2
Compare Source
Bug Fixes
sindresorhus/import-fresh (import-fresh)
v3.3.1
Compare Source
972690b
nodejs/undici (undici)
v6.21.2
Compare Source
What's Changed
New Contributors
Full Changelog: nodejs/undici@v6.21.1...v6.21.2
websockets/ws (ws)
v8.18.1
Compare Source
Bug fixes
make them work when run via CITGM (
021f7b8
).colinhacks/zod (zod)
v3.24.2
Compare Source
Notes
Support asynchronous checks in
z.custom()
.Commits:
cdcf9d4
Bump rollup from 2.79.1 to 2.79.2 (#3895)a2ad370
Bump find-my-way from 8.2.0 to 8.2.2 (#3897)0e02d66
Bump nanoid from 3.3.7 to 3.3.8 (#3896)96be65f
Bump cross-spawn from 7.0.3 to 7.0.6 (#3882)f7ad261
Bump micromatch from 4.0.7 to 4.0.8 (#3748)d724620
Addzod-struct
to utilities for Zod (#3921)6b96cfd
Update README.md (#3949)e376cda
Add Courier to README (#3961)8a099de
Add CodeRabbit to sponsors (#3975)587d160
WIP (#3976)9d3af2e
Add CodeRabbit at Platinum (#3981)eedeb4b
docs(X to Zod): Update url for runtyping (#3971)706f49f
fix: redirect url to correct url (#3939)7365b7d
docs: translate README to Korean (#3934)b7e173d
Format1dd44a0
Support async z.custome308703
v3.24.2Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 8am and before 4pm on tuesday" in timezone America/Los_Angeles.
🚦 Automerge: Enabled.
♻ 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 has been generated by Renovate Bot.