fix(deps): update all non-major dependencies #1901
Open
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:
^1.1.0
->^1.1.2
^7.27.2
->^7.28.0
^8.0.0-beta.0
->^8.0.0-beta.1
^7.27.4
->^7.28.0
^7.27.5
->^7.28.0
^7.27.4
->^7.28.0
^7.27.2
->^7.28.0
^3.21.0
->^3.22.0
^11.14.0
->^11.14.1
^1.3.0
->^1.3.1
^9.29.0
->^9.31.0
^9.0.13
->^9.0.18
^9.0.13
->^9.0.18
^0.0.326
->^0.1.1
^4.17.18
->^4.17.20
^22.15.32
->^22.16.5
^8.35.0
->^8.38.0
^8.35.0
->^8.38.0
^0.25.5
->^0.25.8
^9.29.0
->^9.31.0
^10.1.5
->^10.1.8
^16.2.0
->^16.3.0
^30.0.2
->^30.0.5
^30.0.2
->^30.0.5
^1.10.0
->^1.10.1
^10.1.2
->^10.2.0
10.12.3
->10.13.1
3.6.0
->3.6.2
^7.6.2
->^7.7.0
^5.10.1
->^5.10.2
^4.33.0
->^4.34.0
^9.0.13
->^9.0.18
^7.1.1
->^7.1.4
^8.35.0
->^8.38.0
^7.0.0
->^7.0.5
^5.99.9
->^5.100.2
Release Notes
apollo-server-integrations/apollo-server-integration-express5 (@as-integrations/express5)
v1.1.2
Compare Source
Patch Changes
8217d87
Thanks @glasser! - Allow both v4 and v5 of@apollo/server
as a peer dependency (but not the RC supported by v1.1.1).v1.1.1
Compare Source
Patch Changes
3416827
Thanks @glasser! - Allow@apollo/[email protected]
as a peer dependency.babel/babel (@babel/cli)
v7.28.0
Compare Source
🚀 New Feature
babel-node
babel-types
babel-compat-data
,babel-preset-env
babel-core
,babel-parser
sourceType: "commonjs"
(@JLHwung)babel-generator
,babel-parser
explicitResourceManagement
parser plugin (@JLHwung)babel-plugin-proposal-destructuring-private
,babel-plugin-proposal-do-expressions
,babel-plugin-transform-object-rest-spread
,babel-traverse
,babel-types
babel-parser
,babel-traverse
,babel-types
t.bigIntLiteral
factory (@JLHwung)babel-generator
,babel-plugin-proposal-destructuring-private
,babel-plugin-proposal-discard-binding
,babel-plugin-transform-destructuring
,babel-plugin-transform-explicit-resource-management
,babel-plugin-transform-react-display-name
,babel-types
babel-generator
,babel-parser
,babel-plugin-proposal-destructuring-private
,babel-plugin-transform-block-scoping
,babel-plugin-transform-object-rest-spread
,babel-plugin-transform-typescript
,babel-traverse
,babel-types
🐛 Bug Fix
babel-helper-globals
,babel-plugin-transform-classes
,babel-traverse
babel-types
🏠 Internal
babel-compat-data
,babel-plugin-proposal-decorators
,babel-plugin-transform-async-generator-functions
,babel-plugin-transform-json-modules
,babel-plugin-transform-regenerator
,babel-plugin-transform-runtime
,babel-preset-env
,babel-runtime-corejs3
babel-polyfill
packages (@nicolo-ribaudo)babel/babel (@babel/code-frame)
v8.0.0-beta.1
Compare Source
v8.0.0-beta.1 (2025-07-02)
💥 Breaking Change
babel-plugin-proposal-destructuring-private
,babel-plugin-proposal-do-expressions
,babel-plugin-transform-object-rest-spread
,babel-traverse
,babel-types
babel-parser
,babel-traverse
,babel-types
t.bigIntLiteral
factory (@JLHwung)babel-plugin-proposal-destructuring-private
,babel-plugin-proposal-do-expressions
,babel-plugin-transform-destructuring
,babel-plugin-transform-object-rest-spread
,babel-types
🐛 Bug Fix
babel-types
BABEL_TYPES_8_BREAKING
in Babel 8 (@liuxingbaoyu)🏠 Internal
babel-types
Committers: 9
chakra-ui/chakra-ui (@chakra-ui/react)
v3.22.0
Compare Source
Minor Changes
32967aa
Thanks @segunadebayo! - Add new TreeView
component that is used to represent hierarchical data in a tree structure.
Patch Changes
ca40993
Thanks @isBatak! - - Clipboard: Fix issue
where
clipboardAnatomy
was not exported from@chakra-ui/react/anatomy
reason
toonOpenChange
andonInputValueChange
callbacksapi.clearHighlightedValue
function to clear highlighted valuetitle
ordescription
could not acceptReact element
valueAsString
formattingapi.clearHighlightedValue
function to clear highlighted valuechildren
as a functionv3.21.1
Compare Source
Patch Changes
8ddeb0b
Thanks @segunadebayo! - - Popover:
Fixed issue where
onOpenChange
could be called twice when controlledonInputValueChange
could be called twice whenselecting an item
allowCustomValue: true
used within in aform requires two enter keypress to submit
vertical
don't workdefaultValue
tonull
doesn't showindeterminate state
toaster.promise
is calledwithout loading option. The
loading
option is now required. A warning willbe logged if it is not provided
defaultValue
orvalue
after fetching items doesn't update thevalueAsString
#10119
6cf8cc6
Thanks @isBatak! - - improve
Drawer
recipe tobetter support conditional variants.
Drawer
conditional variants example to the docs and storybook.#10101
2b4fa6d
Thanks @isBatak! - - Select: Export missing
SelectRootComponent type export
d7914ad
Thanks @segunadebayo! - Fix inconsistent
handling of
null
andundefined
for skipping breakpoints using array syntaxemotion-js/emotion (@emotion/styled)
v11.14.1
Compare Source
eslint/rewrite (@eslint/compat)
v1.3.1
Compare Source
Bug Fixes
@eslint/compat
eslint peerDependencies constraint (#215) (b96ec0c)Dependencies
eslint/eslint (@eslint/js)
v9.31.0
Compare Source
v9.30.1
Compare Source
v9.30.0
Compare Source
storybookjs/storybook (@storybook/addon-onboarding)
v9.0.18
Compare Source
9.0.18
v9.0.17
Compare Source
9.0.17
stories.tsx
files - #32041, thanks @ghengeveld!v9.0.16
Compare Source
9.0.16
sb
CLI by explicitly exportingbin/index.cjs
fromstorybook
package - #31922, thanks @ghengeveld!v9.0.15
Compare Source
9.0.15
v9.0.14
Compare Source
9.0.14
vite
peerDependencies range to include7.0.0
- #31859, thanks @ghengeveld!storybookjs/storybook (@storybook/react-vite)
v9.0.18
Compare Source
v9.0.17
Compare Source
stories.tsx
files - #32041, thanks @ghengeveld!v9.0.16
Compare Source
sb
CLI by explicitly exportingbin/index.cjs
fromstorybook
package - #31922, thanks @ghengeveld!v9.0.15
Compare Source
v9.0.14
Compare Source
vite
peerDependencies range to include7.0.0
- #31859, thanks @ghengeveld!typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v8.38.0
Compare Source
🩹 Fixes
isolatedDeclarations
if enabled inconstructor
option (#11351)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.37.0
Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.36.0
Compare Source
This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.35.1
Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v8.38.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.37.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.36.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.35.1
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
evanw/esbuild (esbuild)
v0.25.8
Compare Source
Fix another TypeScript parsing edge case (#4248)
This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the
?:
operator. The regression specifically involves parsing an arrow function containing a#private
identifier inside the middle of a?:
ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:Fix a regression with the parsing of source phase imports
The change in the previous release to parse source phase imports failed to properly handle the following cases:
Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.
v0.25.7
Compare Source
Parse and print JavaScript imports with an explicit phase (#4238)
This release adds basic syntax support for the
defer
andsource
import phases in JavaScript:defer
This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:
Note that this feature deliberately cannot be used with the syntax
import defer foo from "<specifier>"
orimport defer { foo } from "<specifier>"
.source
This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:
Note that this feature deliberately cannot be used with the syntax
import defer * as foo from "<specifier>"
orimport defer { foo } from "<specifier>"
.This change only adds support for this syntax. These imports cannot currently be bundled by esbuild. To use these new features with esbuild's bundler, the imported paths must be external to the bundle and the output format must be set to
esm
.Support optionally emitting absolute paths instead of relative paths (#338, #2082, #3023)
This release introduces the
--abs-paths=
feature which takes a comma-separated list of situations where esbuild should use absolute paths instead of relative paths. There are currently three supported situations:code
(comments and string literals),log
(log message text and location info), andmetafile
(the JSON build metadata).Using absolute paths instead of relative paths is not the default behavior because it means that the build results are no longer machine-independent (which means builds are no longer reproducible). Absolute paths can be useful when used with certain terminal emulators that allow you to click on absolute paths in the terminal text and/or when esbuild is being automatically invoked from several different directories within the same script.
Fix a TypeScript parsing edge case (#4241)
This release fixes an edge case with parsing an arrow function in TypeScript with a return type that's in the middle of a
?:
ternary operator. For example:The
:
token in the value assigned tox
pairs with the?
token, so it's not the start of a return type annotation. However, the first:
token in the value assigned toy
is the start of a return type annotation because after parsing the arrow function body, it turns out there's another:
token that can be used to pair with the?
token. This case is notable as it's the first TypeScript edge case that esbuild has needed a backtracking parser to parse. It has been addressed by a quick hack (cloning the whole parser) as it's a rare edge case and esbuild doesn't otherwise need a backtracking parser. Hopefully this is sufficient and doesn't cause any issues.Inline small constant strings when minifying
Previously esbuild's minifier didn't inline string constants because strings can be arbitrarily long, and this isn't necessarily a size win if the string is used more than once. Starting with this release, esbuild will now inline string constants when the length of the string is three code units or less. For example:
Note that esbuild's constant inlining only happens in very restrictive scenarios to avoid issues with TDZ handling. This change doesn't change when esbuild's constant inlining happens. It only expands the scope of it to include certain string literals in addition to numeric and boolean literals.
v0.25.6
Compare Source
Fix a memory leak when
cancel()
is used on a build context (#4231)Calling
rebuild()
followed bycancel()
in rapid succession could previously leak memory. The bundler uses a producer/consumer model internally, and the resource leak was caused by the consumer being termianted while there were still remaining unreceived results from a producer. To avoid the leak, the consumer now waits for all producers to finish before terminating.Support empty
:is()
and:where()
syntax in CSS (#4232)Previously using these selectors with esbuild would generate a warning. That warning has been removed in this release for these cases.
Improve tree-shaking of
try
statements in dead code (#4224)With this release, esbuild will now remove certain
try
statements if esbuild considers them to be within dead code (i.e. code that is known to not ever be evaluated). For example:Consider negated bigints to have no side effects
While esbuild currently considers
1
,-1
, and1n
to all have no side effectConfiguration
📅 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.
This PR was generated by Mend Renovate. View the repository job log.