chore(deps): update all non-major dependencies (#1099)

renovate[bot] · web-flow · commit a0c6dff018e7 · 2025-07-09T15:51:20.000+10:00
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [esbuild](https://redirect.github.com/evanw/esbuild) | | patch | `0.25.5` -> `0.25.6` | | [go](https://redirect.github.com/golang/go) | | patch | `1.24.4` -> `1.24.5` | | [go](https://go.dev/) ([source](https://redirect.github.com/golang/go)) | toolchain | patch | `1.24.4` -> `1.24.5` | | [uv](https://redirect.github.com/astral-sh/uv) | | patch | `0.7.18` -> `0.7.19` | --- ### Release Notes <details> <summary>evanw/esbuild (esbuild)</summary> ### [`v0.25.6`](https://redirect.github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0256) [Compare Source](https://redirect.github.com/evanw/esbuild/compare/v0.25.5...v0.25.6) - Fix a memory leak when `cancel()` is used on a build context ([#&#8203;4231](https://redirect.github.com/evanw/esbuild/issues/4231)) Calling `rebuild()` followed by `cancel()` 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 ([#&#8203;4232](https://redirect.github.com/evanw/esbuild/issues/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 ([#&#8203;4224](https://redirect.github.com/evanw/esbuild/issues/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: ```js // Original code return 'foo' try { return 'bar' } catch {} // Old output (with --minify) return"foo";try{return"bar"}catch{} // New output (with --minify) return"foo"; ``` - Consider negated bigints to have no side effects While esbuild currently considers `1`, `-1`, and `1n` to all have no side effects, it didn't previously consider `-1n` to have no side effects. This is because esbuild does constant folding with numbers but not bigints. However, it meant that unused negative bigint constants were not tree-shaken. With this release, esbuild will now consider these expressions to also be side-effect free: ```js // Original code let a = 1, b = -1, c = 1n, d = -1n // Old output (with --bundle --minify) (()=>{var n=-1n;})(); // New output (with --bundle --minify) (()=>{})(); ``` - Support a configurable delay in watch mode before rebuilding ([#&#8203;3476](https://redirect.github.com/evanw/esbuild/issues/3476), [#&#8203;4178](https://redirect.github.com/evanw/esbuild/issues/4178)) The `watch()` API now takes a `delay` option that lets you add a delay (in milliseconds) before rebuilding when a change is detected in watch mode. If you use a tool that regenerates multiple source files very slowly, this should make it more likely that esbuild's watch mode won't generate a broken intermediate build before the successful final build. This option is also available via the CLI using the `--watch-delay=` flag. This should also help avoid confusion about the `watch()` API's options argument. It was previously empty to allow for future API expansion, which caused some people to think that the documentation was missing. It's no longer empty now that the `watch()` API has an option. - Allow mixed array for `entryPoints` API option ([#&#8203;4223](https://redirect.github.com/evanw/esbuild/issues/4223)) The TypeScript type definitions now allow you to pass a mixed array of both string literals and object literals to the `entryPoints` API option, such as `['foo.js', { out: 'lib', in: 'bar.js' }]`. This was always possible to do in JavaScript but the TypeScript type definitions were previously too restrictive. - Update Go from 1.23.8 to 1.23.10 ([#&#8203;4204](https://redirect.github.com/evanw/esbuild/issues/4204), [#&#8203;4207](https://redirect.github.com/evanw/esbuild/pull/4207)) This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4673 and CVE-2025-22874) from vulnerability scanners that only detect which version of the Go compiler esbuild uses. - Experimental support for esbuild on OpenHarmony ([#&#8203;4212](https://redirect.github.com/evanw/esbuild/pull/4212)) With this release, esbuild now publishes the [`@esbuild/openharmony-arm64`](https://www.npmjs.com/package/@&#8203;esbuild/openharmony-arm64) npm package for [OpenHarmony](https://en.wikipedia.org/wiki/OpenHarmony). It contains a WebAssembly binary instead of a native binary because Go doesn't currently support OpenHarmony. Node does support it, however, so in theory esbuild should now work on OpenHarmony through WebAssembly. This change was contributed by [@&#8203;hqzing](https://redirect.github.com/hqzing). </details> <details> <summary>golang/go (go)</summary> ### [`v1.24.5`](https://redirect.github.com/golang/go/compare/go1.24.4...go1.24.5) </details> <details> <summary>astral-sh/uv (uv)</summary> ### [`v0.7.19`](https://redirect.github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0719) [Compare Source](https://redirect.github.com/astral-sh/uv/compare/0.7.18...0.7.19) The **[uv build backend](https://docs.astral.sh/uv/concepts/build-backend/) is now stable**, and considered ready for production use. The uv build backend is a great choice for pure Python projects. It has reasonable defaults, with the goal of requiring zero configuration for most users, but provides flexible configuration to accommodate most Python project structures. It integrates tightly with uv, to improve messaging and user experience. It validates project metadata and structures, preventing common mistakes. And, finally, it's very fast — `uv sync` on a new project (from `uv init`) is 10-30x faster than with other build backends. To use uv as a build backend in an existing project, add `uv_build` to the `[build-system]` section in your `pyproject.toml`: ```toml [build-system] requires = ["uv_build>=0.7.19,<0.8.0"] build-backend = "uv_build" ``` In a future release, it will replace `hatchling` as the default in `uv init`. As before, uv will remain compatible with all standards-compliant build backends. ##### Python - Add PGO distributions of Python for aarch64 Linux, which are more optimized for better performance See the [python-build-standalone release](https://redirect.github.com/astral-sh/python-build-standalone/releases/tag/20250702) for more details. ##### Enhancements - Ignore Python patch version for `--universal` pip compile ([#&#8203;14405](https://redirect.github.com/astral-sh/uv/pull/14405)) - Update the tilde version specifier warning to include more context ([#&#8203;14335](https://redirect.github.com/astral-sh/uv/pull/14335)) - Clarify behavior and hint on tool install when no executables are available ([#&#8203;14423](https://redirect.github.com/astral-sh/uv/pull/14423)) ##### Bug fixes - Make project and interpreter lock acquisition non-fatal ([#&#8203;14404](https://redirect.github.com/astral-sh/uv/pull/14404)) - Includes `sys.prefix` in cached environment keys to avoid `--with` collisions across projects ([#&#8203;14403](https://redirect.github.com/astral-sh/uv/pull/14403)) ##### Documentation - Add a migration guide from pip to uv projects ([#&#8203;12382](https://redirect.github.com/astral-sh/uv/pull/12382)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (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](https://redirect.github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/alecthomas/chroma).  Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
diff --git a/bin/.esbuild-0.25.6.pkg b/bin/.esbuild-0.25.6.pkg
diff --git a/bin/.go-1.24.5.pkg b/bin/.go-1.24.5.pkg
diff --git a/bin/.uv-0.7.19.pkg b/bin/.uv-0.7.19.pkg
diff --git a/bin/esbuild b/bin/esbuild
@@ -1 +1 @@
-.esbuild-0.25.5.pkg
+.esbuild-0.25.6.pkg
diff --git a/bin/go b/bin/go
@@ -1 +1 @@
-.go-1.24.4.pkg
+.go-1.24.5.pkg
diff --git a/bin/gofmt b/bin/gofmt
@@ -1 +1 @@
-.go-1.24.4.pkg
+.go-1.24.5.pkg
diff --git a/bin/uv b/bin/uv
@@ -1 +1 @@
-.uv-0.7.18.pkg
+.uv-0.7.19.pkg
diff --git a/bin/uvx b/bin/uvx
@@ -1 +1 @@
-.uv-0.7.18.pkg
+.uv-0.7.19.pkg
diff --git a/cmd/chroma/go.mod b/cmd/chroma/go.mod
@@ -2,7 +2,7 @@ module github.com/alecthomas/chroma/v2/cmd/chroma
 
 go 1.22
 
-toolchain go1.24.4
+toolchain go1.24.5
 
 replace github.com/alecthomas/chroma/v2 => ../../
 
diff --git a/cmd/chromad/go.mod b/cmd/chromad/go.mod
@@ -2,7 +2,7 @@ module github.com/alecthomas/chroma/v2/cmd/chromad
 
 go 1.22
 
-toolchain go1.24.4
+toolchain go1.24.5
 
 require (
 	github.com/alecthomas/chroma/v2 v2.19.0

Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		`-.esbuild-0.25.5.pkg`
	`1`	`+.esbuild-0.25.6.pkg`