Bump the "dependencies" group with 2 updates across multiple ecosystems

[dependabot]

Bumps the dependencies group with 1 update: jdx/mise-action.

Updates jdx/mise-action from 4 to 4.2.3

Release notes

Sourced from jdx/mise-action's releases.

v4.2.3: Restore mise PATH propagation

A patch release that restores mise's PATH propagation to subsequent workflow steps — without reintroducing the full-PATH snapshot behavior that v4.2.1 fixed.

Fixed

Export mise PATH entries to subsequent steps (#575) by @​jdx

v4.2.1 stopped exporting the complete PATH returned by mise env --json into GITHUB_ENV, which correctly prevented snapshotting the runner's environment into subsequent steps. However, that also dropped mise-produced PATH entries — tool shims, [env] _.path directories, and similar — that workflows relied on after the setup step. See #565.

The action now computes only the prefix that mise prepended to the existing PATH and forwards those directories individually through GITHUB_PATH. This preserves mise's configured ordering, composes cleanly with PATH changes from other actions, and never persists the runner's full PATH through GITHUB_ENV. The dotenv fallback path (used with older mise versions) also strips PATH= lines and re-derives additions from mise env --json.

A new export_path input (default true) lets workflows keep regular env exports while opting out of PATH changes:

- uses: jdx/mise-action@v4
  with:
    export_path: false # keep env vars, skip mise PATH additions

Full Changelog: jdx/mise-action@v4.2.2...v4.2.3

v4.2.2: Zstd tar fallback for older runners

A small patch release that fixes archive selection on runners with an older tar and corrects a stale default in the README.

Fixed

Verify tar supports Zstd before picking .tar.zst (#569 by @​JackMyers001

The action previously chose the .tar.zst mise archive whenever zstd --version succeeded, then extracted it with tar --zstd. On RHEL 8-compatible runners that ship zstd 1.4.4 alongside GNU tar 1.30, the --zstd option isn't recognized and installation failed.

Detection now runs both checks:

zstd --version
tar --zstd --version

If either fails, the action falls back to the .tar.gz archive. No configuration change is required — existing workflows on affected runners just start working again. Fixes #568.

Documentation

• Update the cache_key_prefix example in the README to reflect the current default of mise-v1 (previously documented as mise-v0) (#570 by @​muzimuzhi).

New Contributors

• @​JackMyers001 made their first contribution in #569
• @​muzimuzhi made their first contribution in #570

Full Changelog: jdx/mise-action@v4.2.1...v4.2.2

... (truncated)

Changelog

Sourced from jdx/mise-action's changelog.

Commits

• d44584d chore(deps): update dependency js-yaml to v5.2.1 (#550)
• 4b4b9b2 chore(release): skip ai reviews for release prs (#549)
• 0f03c79 fix: verify mise downloads with signed checksums (#548)
• 6bd511f chore(deps): update dependency js-yaml to v5.2.0 (#546)
• 9e61cb6 chore(deps): update dependency eslint to v10.6.0 (#545)
• 7705944 chore(deps): update dependency prettier to v3.8.5 (#544)
• 770ac38 chore(deps): update dependency js-yaml to v5 (#543)
• 096fded chore(deps): update dependency typescript-eslint to v8.62.0 (#542)
• See full diff in compare view

Updates the requirements on typing-extensions and uv-build to permit the latest version.
Updates typing-extensions to 4.16.0

Release notes

Sourced from typing-extensions's releases.

4.16.0

No changes since 4.16.0rc2.

Changes since 4.15.0:

• Make typing_extensions.TypeAliasType's __module__ attribute writable. Backport of CPython PR #149172.
• Fix setting of __required_keys__ and __optional_keys__ when inheriting keys with the same name.
• Add support for AsyncIterator, io.Reader, io.Writer and os.PathLike protocols as bases for other protocols.
• Fix incorrect behaviour on Python 3.9 and Python 3.10 that meant that calling isinstance with typing_extensions.Concatenate[...] or typing_extensions.Unpack[...] as the first argument could have a different result in some situations depending on whether or not a profiling function had been set using sys.setprofile. This affected both CPython and PyPy implementations. Patch by Brian Schubert.
• Fix __init_subclass__() behavior in the presence of multiple inheritance involving an @deprecated-decorated base class. Backport of CPython PR #138210 by Brian Schubert.
• Raise TypeError when attempting to subclass typing_extensions.ParamSpec on Python 3.9. The typing implementation has always raised an error, and the typing_extensions implementation has raised an error on Python 3.10+ since typing_extensions v4.6.0. Patch by Brian Schubert.
• Add the bound, covariant, contravariant, and infer_variance parameters to TypeVarTuple.
• Officially support the bound, covariant, contravariant and infer_variance parameters to ParamSpec. Improve the validation of these parameters at runtime.
• Rename typing_extensions.Sentinel to typing_extensions.sentinel, following the name that has been adopted for builtins.sentinel on Python 3.15. typing_extensions.Sentinel is retained as a soft-deprecated alias for backwards compatibility.
• Add support for pickling sentinels.
• Sentinels now preserve their identity when copied or deep-copied.
• Deprecate passing name as a keyword argument or repr as a positional argument to the sentinel constructor.
• The default repr of a sentinel X = sentinel("X") is now X rather than <X>.
• Deprecate arbitrary attribute assignments to sentinels.
• Deprecate subclassing sentinels.
• Add support for Python 3.15.
• Avoid a DeprecationWarning when deprecated is applied to a coroutine function on Python 3.14.0.

Changelog

Sourced from typing-extensions's changelog.

Release 4.16.0 (July 2, 2025)

No user-facing changes since 4.16.0rc2.

Release 4.16.0rc2 (June 25, 2026)

• Avoid a DeprecationWarning when deprecated is applied to a coroutine function on Python 3.14.0.

Release 4.16.0rc1 (June 24, 2026)

• Make typing_extensions.TypeAliasType's __module__ attribute writable. Backport of CPython PR #149172.
• Fix setting of __required_keys__ and __optional_keys__ when inheriting keys with the same name.
• Add support for AsyncIterator, io.Reader, io.Writer and os.PathLike protocols as bases for other protocols.
• Fix incorrect behaviour on Python 3.9 and Python 3.10 that meant that calling isinstance with typing_extensions.Concatenate[...] or typing_extensions.Unpack[...] as the first argument could have a different result in some situations depending on whether or not a profiling function had been set using sys.setprofile. This affected both CPython and PyPy implementations. Patch by Brian Schubert.
• Fix __init_subclass__() behavior in the presence of multiple inheritance involving an @deprecated-decorated base class. Backport of CPython PR #138210 by Brian Schubert.
• Raise TypeError when attempting to subclass typing_extensions.ParamSpec on Python 3.9. The typing implementation has always raised an error, and the typing_extensions implementation has raised an error on Python 3.10+ since typing_extensions v4.6.0. Patch by Brian Schubert.
• Add the bound, covariant, contravariant, and infer_variance parameters to TypeVarTuple.
• Officially support the bound, covariant, contravariant and infer_variance parameters to ParamSpec. Improve the validation of these parameters at runtime.
• Rename typing_extensions.Sentinel to typing_extensions.sentinel, following the name that has been adopted for builtins.sentinel on Python 3.15. typing_extensions.Sentinel is retained as a soft-deprecated alias for backwards compatibility.
• Add support for pickling sentinels.
• Sentinels now preserve their identity when copied or deep-copied.
• Deprecate passing name as a keyword argument or repr as a positional argument to the sentinel constructor.
• The default repr of a sentinel X = sentinel("X") is now X rather than <X>.
• Deprecate arbitrary attribute assignments to sentinels.
• Deprecate subclassing sentinels.
• Add support for Python 3.15.

Release 4.15.0 (August 25, 2025)

... (truncated)

Commits

• f29cd28 Prepare relase 4.16.0 (#774)
• 4317461 Bump version to 4.16.0rc2.dev (#772)
• 4f71098 Prepare release 4.16.0rc2 (#771)
• 37ed08a Remove use of asyncio.coroutines.iscoroutinefunction() (#769)
• 8dcc559 Improve TypedDict documentation (#770)
• 224f8d5 Post-release followups for 3.16.0rc1 (#767)
• 777de3e Prepare release 4.16.0rc1 (#766)
• 890be90 Type variable tuple variance (#741)
• 0e05458 Pin SQLAlchemy third-party tests to pytest==9.0.3 (#765)
• d277746 docs: add version compatibility table (#733)
• Additional commits viewable in compare view

Updates uv-build to 0.12.0

Release notes

Sourced from uv-build's releases.

0.12.0

Release Notes

Released on 2026-07-28.

Since we released uv 0.11.0 in March, we've accumulated changes that improve correctness, safety, and compatibility with specifications, but could break some workflows. This release contains those changes; many have been marked as breaking out of an abundance of caution.

We expect most users to be able to upgrade without making changes.

There are no breaking changes to the configuration of the uv build backend. If your [build-system] table includes an upper bound on uv_build, update it to allow uv_build 0.12, e.g., uv_build>=0.11.32,<0.13.

Breaking changes

• Define build systems by default with uv init (#19197)

  Projects created with uv init now declare a build system and are packaged by default. This was the default project layout all the way back in v0.3, but we found that the use of the hatchling build system was confusing to newcomers and consequently dropped use of a build system by default in v0.4. Since then, we've created our own build system (uv_build) with tight integration with uv and are excited to restore the default to a best-practice project layout.

  Previously, uv init example created an unpackaged layout containing main.py and a pyproject.toml without a build system. The project could declare dependencies but was not itself installed into its virtual environment.

  Now, uv init example defines a [build-system] using uv_build, places application source code in src/example, and includes a [project.scripts] entry named example. Defining a build system allows the project to be imported from tests or other code, installed as a dependency, and run as a command:

  $ uv init example
  $ cd example
  $ uv run example
  Hello from example!

  Existing projects are unaffected. Use uv init --no-package example to create the previous unpackaged layout without a build system.

  See the project creation documentation for more details.

  This stabilizes the packaged-init preview feature.

• Reject unsupported source distribution and wheel archive formats (#18927)

  PEP 625 requires source distributions to use .tar.gz archives. Previously, uv also accepted legacy formats such as .tar.bz2 and .tar.xz. Those formats are now rejected, including when referenced by an existing lockfile. Legacy .zip source distributions remain supported for backwards compatibility.

  Wheels and other ZIP archives can no longer contain entries compressed with bzip2, LZMA, or XZ. Entries must use the stored, DEFLATE, or zstd compression methods.

  Removing support for uncommon compression methods reduces uv's compression dependencies and the attack surface exposed when processing untrusted packages.

  You cannot opt out of this behavior. If you depend on a legacy source distribution that uses an unsupported format, we recommend rebuilding it as a .tar.gz archive and regenerating any lockfile containing references to the legacy archive.

• Reject wheel files that could replace the Python interpreter (#20748, #20749)

  uv already rejected wheel entry points named python, but case variants such as Python were still accepted. On case-insensitive filesystems, including common macOS and Windows setups, these entry points could overwrite the virtual environment's interpreter.

  Wheels could also place interpreter files in their .data/scripts directory or in paths such as .data/data/bin/python, bypassing the entry-point check and replacing the interpreter during installation.

... (truncated)

Changelog

Sourced from uv-build's changelog.

0.12.0

Released on 2026-07-28.

Since we released uv 0.11.0 in March, we've accumulated changes that improve correctness, safety, and compatibility with specifications, but could break some workflows. This release contains those changes; many have been marked as breaking out of an abundance of caution.

We expect most users to be able to upgrade without making changes.

There are no breaking changes to the configuration of the uv build backend. If your [build-system] table includes an upper bound on uv_build, update it to allow uv_build 0.12, e.g., uv_build>=0.11.32,<0.13.

Breaking changes

• Define build systems by default with uv init (#19197)

  Projects created with uv init now declare a build system and are packaged by default. This was the default project layout all the way back in v0.3, but we found that the use of the hatchling build system was confusing to newcomers and consequently dropped use of a build system by default in v0.4. Since then, we've created our own build system (uv_build) with tight integration with uv and are excited to restore the default to a best-practice project layout.

  Previously, uv init example created an unpackaged layout containing main.py and a pyproject.toml without a build system. The project could declare dependencies but was not itself installed into its virtual environment.

  Now, uv init example defines a [build-system] using uv_build, places application source code in src/example, and includes a [project.scripts] entry named example. Defining a build system allows the project to be imported from tests or other code, installed as a dependency, and run as a command:

  $ uv init example
  $ cd example
  $ uv run example
  Hello from example!

  Existing projects are unaffected. Use uv init --no-package example to create the previous unpackaged layout without a build system.

  See the project creation documentation for more details.

  This stabilizes the packaged-init preview feature.

• Reject unsupported source distribution and wheel archive formats (#18927)

  PEP 625 requires source distributions to use .tar.gz archives. Previously, uv also accepted legacy formats such as .tar.bz2 and .tar.xz. Those formats are now rejected, including when referenced by an existing lockfile. Legacy .zip source distributions remain supported for backwards compatibility.

  Wheels and other ZIP archives can no longer contain entries compressed with bzip2, LZMA, or XZ. Entries must use the stored, DEFLATE, or zstd compression methods.

  Removing support for uncommon compression methods reduces uv's compression dependencies and the attack surface exposed when processing untrusted packages.

  You cannot opt out of this behavior. If you depend on a legacy source distribution that uses an unsupported format, we recommend rebuilding it as a .tar.gz archive and regenerating any lockfile containing references to the legacy archive.

• Reject wheel files that could replace the Python interpreter (#20748, #20749)

  uv already rejected wheel entry points named python, but case variants such as Python were still accepted. On case-insensitive filesystems, including common macOS and Windows setups, these entry points could overwrite the virtual environment's interpreter.

  Wheels could also place interpreter files in their .data/scripts directory or in paths such as .data/data/bin/python, bypassing the entry-point check and replacing the interpreter during installation.

  uv now rejects case-insensitive variants of reserved interpreter names and wheel data files that would be installed over an interpreter. This includes names such as Python, python.py, and Python.exe, along with other reserved interpreter names and their versioned variants.

  You cannot opt out of these checks. Rename conflicting entry points or wheel data files and rebuild the affected wheel.

... (truncated)

Commits

• b88d7c5 Archive the 0.11.x changelog (#20777)
• faff952 Update Rust crate jiff to v0.2.34 (#20710)
• 4c28d9c Keep changelog paragraphs on single lines (#20778)
• 43a1288 Bump version to 0.12.0 (#20775)
• 8fe5f80 Sync latest Python releases (#20682)
• b187a51 Honor certificate overrides when running remote scripts (#20767)
• 6e79013 Package explicitly requested applications by default (#20773)
• e4602de Reject broken .venv symlinks and surface metadata errors (#20433)
• 9391f97 Reject multi-dot pylock filenames (#20440)
• 06bba12 Honor explicit certificate sources even when empty (#20741)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[github-actions]

📖 Docs Preview

Preview of the documentation for this PR:

🔗 https://smokeshow.helpmanual.io/6i5q530r2j1h3e46441n/

_{Built from 1b30022}