fix(deps): update all non-major dependencies #1424
Merged
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}
🦋 Changeset detectedLatest commit: d15a69f The changes in this PR will be included in the next version bump. This PR includes changesets to release 34 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Size Change: +15 B (0%) Total Size: 569 kB
ℹ️ View Unchanged
|
Niznikr
approved these changes
Oct 1, 2024
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:
3.5.5->3.5.63.9.8->3.10.03.14.6->3.14.73.10.3->3.10.43.18.2->3.18.33.9.3->3.9.43.12.2->3.12.33.22.2->3.22.33.7.11->3.7.123.13.3->3.13.43.3.4->3.4.03.15.3->3.15.43.11.6->3.11.73.23.2->3.23.33.14.9->3.14.103.19.3->3.20.03.4.2->3.4.33.6.7->3.6.83.15.3->3.15.43.9.5->3.9.63.4.5->3.4.63.14.8->3.14.93.0.0-beta.15->3.0.0-beta.163.25.2->3.25.33.8.15->3.8.163.10.9->3.11.03.10.9->3.11.03.10.9->3.11.03.9.2->3.10.03.11.6->3.11.73.10.8->3.11.03.8.2->3.8.33.9.6->3.9.73.6.10->3.6.113.6.7->3.6.83.16.2->3.17.03.12.2->3.12.33.12.2->3.12.33.6.9->3.6.103.0.0-beta.5->3.0.0-beta.63.7.7->3.7.83.10.3->3.10.43.9.6->3.10.03.12.1->3.13.03.2.8->3.2.93.8.9->3.8.103.9.6->3.9.73.24.1->3.25.03.24.1->3.25.03.3.9->3.3.10^1.15.0->^1.16.00.23.1->0.24.03.34.3->3.35.01.3.3->1.4.03.32.2->3.33.0^1.90.0->^1.93.1Release Notes
adobe/react-spectrum (@internationalized/date)
v3.5.6Compare Source
adobe/react-spectrum (@react-aria/button)
v3.10.0Compare Source
vanilla-extract-css/vanilla-extract (@vanilla-extract/css)
v1.16.0Compare Source
Minor Changes
#1475
cd9d8b2Thanks @corradopetrelli! - Add::-webkit-calendar-picker-indicatoras a valid pseudo-element#1450
7b256d2Thanks @wuz! - AddcreateViewTransitionAPIcreateViewTransitioncreates a single scoped view transition name for use with CSS View Transitions. This avoids potential naming collisions with other view transitions.evanw/esbuild (esbuild)
v0.24.0Compare Source
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of
esbuildin yourpackage.jsonfile (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.23.0or~0.23.0. See npm's documentation about semver for more information.Drop support for older platforms (#3902)
This release drops support for the following operating system:
This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.
Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:
Fix class field decorators in TypeScript if
useDefineForClassFieldsisfalse(#3913)Setting the
useDefineForClassFieldsflag tofalseintsconfig.jsonmeans class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.Avoid incorrect cycle warning with
tsconfig.jsonmultiple inheritance (#3898)TypeScript 5.0 introduced multiple inheritance for
tsconfig.jsonfiles whereextendscan be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release,tsconfig.jsonfiles containing this edge case should work correctly without generating a warning.Handle Yarn Plug'n'Play stack overflow with
tsconfig.json(#3915)Previously a
tsconfig.jsonfile thatextendsanother file in a package with anexportsmap could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.Work around more issues with Deno 1.31+ (#3917)
This version of Deno broke the
stdinandstdoutproperties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. whenimport.meta.mainistrue). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.This fix was contributed by @Joshix-1.
microsoft/vscode (vscode)
v1.93.1: August 2024 Recovery 1Compare Source
The update addresses these issues.
For the complete release notes go to Updates on code.visualstudio.com.
v1.93.0: August 2024Compare Source
Welcome to the August 2024 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:
v1.92.2: July 2024 Recovery 2Compare Source
The update addresses these issues.
For the complete release notes go to Updates on code.visualstudio.com.
v1.92.1: July 2024 Recovery 1Compare Source
The update addresses these issues.
For the complete release notes go to Updates on code.visualstudio.com.
v1.92.0: July 2024Compare Source
Welcome to the July 2024 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:
v1.91.1: June 2024 Recovery 1[Compare Source](https://redirect.github.com/micr
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (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 was generated by Mend Renovate. View the repository job log.