Update dependencies #44

renovate · 2024-09-23T00:06:24Z

This PR contains the following updates:

Package	Type	Update	Change
clap	workspace.dependencies	patch	`4.5.16` -> `4.5.18`
esbuild	devDependencies	minor	`^0.23.0` -> `^0.24.0`
grep-regex (source)	workspace.dependencies	patch	`0.1.12` -> `0.1.13`
grep-searcher (source)	workspace.dependencies	patch	`0.1.13` -> `0.1.14`
insta (source)	workspace.dependencies	minor	`1.39.0` -> `1.40.0`
serde (source)	workspace.dependencies	patch	`1.0.209` -> `1.0.210`
serde_json	workspace.dependencies	patch	`1.0.127` -> `1.0.128`
syn	workspace.dependencies	patch	`2.0.76` -> `2.0.77`
thiserror	workspace.dependencies	patch	`1.0.63` -> `1.0.64`

Release Notes

clap-rs/clap (clap)

`v4.5.18`

Compare Source

Features

(builder) Expose Arg::get_display_order and Command::get_display_order

`v4.5.17`

Compare Source

Fixes

(help) Style required argument groups
(derive) Improve error messages when unsupported fields are used

evanw/esbuild (esbuild)

`v0.24.0`

Compare 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 esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.23.0 or ~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:
- macOS 10.15 Catalina
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:
```
git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild --version
```
Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

Setting the useDefineForClassFields flag to false in tsconfig.json means 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.json multiple inheritance (#3898)

TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can 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.json files 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.json file that extends another file in a package with an exports map 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 stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). 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.

BurntSushi/ripgrep (grep-regex)

`v0.1.13`

Compare Source

Windows release

mitsuhiko/insta (insta)

`v1.40.0`

Compare Source

cargo-insta no longer panics when running cargo insta test --accept --workspace
on a workspace with a default crate. #532
MSRV for insta has been raised to 1.60, and for cargo-insta to 1.64.
Added support for compact debug snapshots (assert_compact_debug_snapshot). #514
Deprecate --no-force-pass in cargo-insta. The --check option covers the
same functionality and has a clearer name. #513
Inline snapshots now use the required number of #s to escape the snapshot
value, rather than always using ###. This allows snapshotting values which
themselves contain ###. If there are no existing # characters in the
snapshot value, a single # will be used. #540
Inline snapshots can now be updated with --force-update-snapshots. #569
cargo insta test accepts multiple --exclude flags. #520
test runner in insta's yaml config works. #544
Print a warning when encountering old snapshot formats. #503
Group the options in cargo insta --help, upgrade to clap from structopt. #518
No longer suggest running cargo insta message when running cargo insta test --check. #515
Print a clearer error message when accepting a snapshot that was removed. #516
Mark require-full-match as experimental, given some corner-cases are currently difficult to manage. #497
Add a new integration test approach for cargo-insta and a set of integration tests. #537
Enable Filters to be created from IntoIterator types, rather than just Vecs. #570
Implemented total sort order for an internal Key type correctly. This prevents potential
crashes introduced by the new sort algorithm in Rust 1.81. #586

serde-rs/serde (serde)

`v1.0.210`

Compare Source

Support serializing and deserializing IpAddr and SocketAddr in no-std mode on Rust 1.77+ (#2816, thanks @MathiasKoch)
Make serde::ser::StdError and serde::de::StdError equivalent to core::error::Error on Rust 1.81+ (#2818)