chore(deps): update docker

[bootc-bot]

This PR contains the following updates:

Package	Update	Change
astral-sh/uv	patch	0.12.1 → 0.12.3
jj-vcs/jj	minor	0.43.0 → 0.44.0
nextest-rs/nextest	patch	0.9.140 → 0.9.143
rust-nightly	patch	nightly-2026-08-03 → nightly-2026-08-10

---

Release Notes

astral-sh/uv (astral-sh/uv)

v0.12.3

Compare Source

Released on 2026-08-07.

Python

• Add CPython 3.13.15 (#​20997)

Preview features

• Add --output-format to select automatic, human-readable, or raw-byte output for uv cache size (#​20992)
• Preserve JSON output from uv workspace metadata --quiet while suppressing diagnostics (#​20991)
• Reduce memory usage for large workspaces by streaming uv workspace metadata JSON output (#​20990)

Performance

• Reduce Linux startup latency by initializing the workspace cache before spawning another thread (#​20989)
• Reuse compiled workspace exclusion patterns during workspace discovery (#​20988)
• Speed up conflict-heavy resolutions by avoiding materialized range complements (#​20982)
• Avoid slow procfs reads during Python interpreter discovery on Linux (#​20987)

Documentation

• Add PEP 740 attestations to the GitHub Actions publishing example (#​20986)
• Restrict the GitHub Actions publishing example to Python version tags (#​20973)
• Correct --python-pin to --pin-python in the uv init --bare example (#​20876)

v0.12.2

Compare Source

Released on 2026-08-05.

Python

• Add CPython 3.15.0rc1 (#​20948)
• Add CPython 3.14.7 (#​20971)

Enhancements

• Ensure diagnostic hints end with a newline to prevent malformed terminal output (#​20959)

Preview features

• Audit one or all installed tools with uv tool audit (#​20921)
• Report physically reclaimed disk space during cache cleanup with the cache-physical-space preview feature (#​20925)

Configuration

• Add UV_RUN_RLIMIT_NOFILE to set the open-file limit for commands launched by uv run (#​20926)

Performance

• Speed up uv.lock parsing for wheel entries (#​20881)
• Speed up uv.lock parsing for source distribution entries (#​20882)
• Speed up filename extraction from distribution URLs (#​20879)
• Reduce filesystem metadata lookups during bytecode compilation (#​20928)
• Reuse file metadata when building source distributions (#​20927)

Bug fixes

• Preserve compatibility with older uv versions when recording artifact sizes in cached wheels and source distributions (#​20963)
• Avoid including workspace-root default dependency groups when syncing or exporting a selected workspace member unless explicitly requested (#​20930)

Documentation

• Separate build and publish jobs in the GitHub Actions publishing guide (#​20946)
• Ensure the GitHub Actions publishing example waits for the build job to finish (#​20957)
• Correct typos in the Docker integration guide (#​20970)

jj-vcs/jj (jj-vcs/jj)

v0.44.0

Compare Source

About

jj is a Git-compatible version control system that is both simple and powerful. See
the installation instructions to get started.

Release highlights

• Support for fetching and pushing tags has now been stabilized. Tags can be
  tracked or untracked just like bookmarks. Tracked tags are pushed by default.

Breaking changes

• jj git fetch now fetches tags the same way it fetches bookmarks. Tags are
  fetched as <name>@<remote>, and these remote tags are automatically tracked
  by local tags of the same name. Running jj git fetch in an existing
  repository will re-fetch all tags to initialize the tracking state.

  Git's tagOpt is no longer respected. To disable tag fetching, set
  remotes.<name>.fetch-tags = '~*' in the jj configuration.

• jj git clone --fetch-tags=all|none|included is removed in favor of
  --tag=PATTERN.

• jj git push --all now pushes all tags in addition to bookmarks.

• The WorkspaceRef.root() and RepoPath.absolute() template functions now
  return Option<FsPath> and FsPath respectively, instead of String. The
  path keyword in jj config list templates now returns Option<FsPath>.

• jj file search now prints every matched line prefixed by the file path,
  instead of only the file paths of files containing a match. Use
  --name-only for the previous behavior.
  #​9399

• Passing an argument more than once is no longer an error. The last occurrence
  wins, so jj --no-pager --no-pager version and jj log -n 5 -n 10 now work,
  and an argument baked into an alias or a wrapper can be given explicitly as
  well. Arguments that can be specified multiple times, such as --config and
  jj log -r, are unaffected and still collect all of their values.
  #​8101
  #​9859

Deprecations

None

New features

• New merge_point() revset function which (similar to fork_point) finds the
  point where multiple branches merge.

• jj workspace list now shows workspace roots by default. The output can be
  customized with templates.workspace_list or -T, and WorkspaceRef.root()
  returns an optional FsPath value.
  #​9713,
  #​9826

• New try(expr, fallback...) template function to suppress runtime errors.

• jj run now processes revisions from oldest to newest by default. The start
  order is guaranteed: each revision begins execution only after the previous
  one has started, even with --jobs higher than 1.

• jj run gained a --passthrough flag that connects the subprocess's
  stdout/stderr directly to the terminal instead of capturing output.

• jj run gained a --ignore-changes flag to avoid editing any revisions even
  if the command modifies the working copy.

• jj run gained a --ignore-errors flag to continue running against the
  remaining revisions even if the command exits with a nonzero exit code.

• jj file search now supports -n/--line-number to prefix each match with
  its 1-based line number within the file.

• jj git push gained a --allow-conflicts flag to allow pushing commits
  containing conflicts.

• New jj tag track/untrack commands to associate local tags with remotes.
  Note that fetched tags are tracked by default.

• Added builtin_log() revset alias for the built-in default jj log revset.
  revsets.log now defaults to builtin_log(), so custom log revsets can
  reuse the built-in default instead of copying its full expression.

• Added config option diff.stat.max-bar-width for use with --stat to limit
  the ++-- bar width. In the templating language, diff.stat() can optionally
  take a second (positional or named) argument max_bar_width for an equivalent
  effect.

• jj absorb now supports --interactive/-i/--tool to let you
  interactively choose which hunks from the source to consider for absorption.
  This is useful when you only want to absorb part of a commit without first
  splitting it. Any hunks that are not selected or cannot be absorbed remain in
  the source commit.

Fixed bugs

• Recursive alias definitions are detected more precisely. jj can now expand
  aliases that are simply repeated. For example, with the alias jj = [], the
  command jj jj jj will resolve to jj. Aliases can also fall back to the
  default command. For example, with the alias i = ["--ignore-working-copy"],
  jj i will resolve to jj --ignore-working-copy.

• Git temporary files are now cleaned up more reliably in the presence of
  signals (e.g. Ctrl-C). This should reduce the rate of "Could not acquire
  lock for index file" errors.
  (#​7530)

• Fixed Git HEAD mismatch after the working copy became immutable.
  #​9827

• jj now creates a new working-copy revision as soon as the one of the current
  workspace becomes immutable, as well as during snapshotting. This brings the
  behavior closer to jj 0.42 and earlier.

• Snapshotting no longer fails if the working copy contains a path whose name
  isn't valid UTF-8. Such paths can't be tracked, so they are now skipped and
  reported as a warning instead.
  #​9774

• Fixed failure when reading configuration in copied repo with an empty
  repo-level configuration directory.

• jj diff and jj status no longer omit a rename or copy in a merge commit
  when the renamed source is present in more than one parent. The identical copy
  record reported for each parent was mistaken for a conflict and discarded.
  #​9752

• jj run no longer panics when its revset includes a conflicted commit. The
  conflict is now preserved in the rewritten commit.
  #​9747

• Fixed a panic when passing overly-large length parameters to ID templater
  functions (commit_id.short(), commit_id.shortest(), etc.).
  #​9833

• jj git import and export in colocated workspaces are now disabled by
  default. These commands usually do nothing, but they had a race condition.

Contributors

Thanks to the people who made this release happen!

• Aaron Bies (@​slerpyyy)
• Ada Alakbarova (@​ada4a)
• Alexandre Hallaine (@​alexandre-hallaine)
• Amaan Qureshi (@​amaanq)
• Austin Seipp (@​thoughtpolice)
• Caleb White (@​calebdw)
• Chawye Hsu (@​chawyehsu)
• David Rieber (@​drieber)
• Gaëtan Lehmann (@​glehmann)
• hexbinoct (@​hexbinoct)
• ivelieu (@​ivelieu)
• Joseph Lou (@​josephlou5)
• Josh McKinney (@​joshka)
• Josh Steadmon (@​steadmon)
• Kevin Liao (@​kevincliao)
• Luna Schwalbe (@​lunagl)
• Martin von Zweigbergk (@​martinvonz)
• Matt Van Horn (@​mvanhorn)
• Nika Layzell (@​mystor)
• Niko Savola (@​nikosavola)
• Nitzan Raz (@​BackSlasher)
• Noah Lev (@​camelid)
• OlshaMB (@​OlshaMB)
• Philip Metzger (@​PhilipMetzger)
• Remo Senekowitsch (@​senekor)
• Rob Pilling (@​bobrippling)
• Stephen Jennings (@​jennings)
• Techcable (@​Techcable)
• TogarashiPepper (@​TogarashiPepper)
• Vladimir Petrzhikovskii (@​0xdeafbeef)
• Waleed Khan (@​arxanas)
• Wang Yuantao (@​0WD0)
• xtqqczze (@​xtqqczze)
• Yash Bavadiya (@​xevrion)
• Yuya Nishihara (@​yuja)

nextest-rs/nextest (nextest-rs/nextest)

v0.9.143: cargo-nextest 0.9.143

Compare Source

Added

• A new junit.report-skipped configuration setting controls which skipped tests are emitted in the JUnit XML report as <testcase> elements with a <skipped> child. (#​885)

  Thanks to liangfu for your first contribution!

• While listing tests, nextest now shows a progress bar if listing takes longer than 2 seconds. Listing is usually fast, but can be slow in some environments, such as with antivirus software that scans each test binary before it runs. (#​3471)

• The binaries metadata (used by archives and --binaries-metadata) now records whether Cargo built each non-test binary for the host or the target platform. Future versions of nextest will use this to configure environment variables correctly in cross-compilation scenarios. (#​3520)

Changed

• Nextest now orders the dynamic library search path the way current versions of Cargo do, with the Cargo artifact directory ahead of the deps directory. Previously the two were reversed, so a test could potentially resolve a dylib to a different copy than cargo test would. (Cargo swapped the two in 1.93.)

Fixed

• Nextest now computes the dynamic library search path correctly under build directory layout v2, which became the default on nightly Rust on 2026-07-30. Previously, tests that linked against a dylib dependency failed to start because the dynamic library could not be found.
• When Cargo's build.build-dir is configured, nextest now adds the Cargo artifact directory (where final artifacts like binaries and dynamic libraries are uplifted to) instead of the build directory (for intermediate artifacts) to the dynamic library search path. This matches Cargo's behavior.
• Nextest now detects the base output directory for test binaries built from [[example]] targets, which Cargo places in examples rather than deps. Previously, a run restricted to examples didn't add anything to the dynamic library search path, so an example test linking against a dylib failed to start.
• While creating an archive with a filterset, nextest now always includes dynamic libraries in the archive, even those from packages whose test binaries are all filtered out. Dynamic libraries are on the library search path and may be loaded by tests in other packages. Binaries exposed via CARGO_BIN_EXE_<name> are still filtered out if no test binaries from that package are selected. (#​3516)
• The "Archiving" message now counts non-test binaries correctly. Previously, nextest counted the number of packages containing non-test binaries rather than the number of binaries. (#​3515)

v0.9.142: cargo-nextest 0.9.142

Compare Source

Added

• A new junit.report-skipped configuration setting controls which skipped tests are emitted in the JUnit XML report as <testcase> elements with a <skipped> child. (#​885)

  Thanks to liangfu for your first contribution!

• While listing tests, nextest now shows a progress bar if listing takes longer than 2 seconds. Listing is usually fast, but can be slow in some environments, such as with antivirus software that scans each test binary before it runs. (#​3471)

• The binaries metadata (used by archives and --binaries-metadata) now records whether Cargo built each non-test binary for the host or the target platform. Future versions of nextest will use this to configure environment variables correctly in cross-compilation scenarios. (#​3520)

Changed

• Nextest now orders the dynamic library search path the way current versions of Cargo do, with the Cargo artifact directory ahead of the deps directory. Previously the two were reversed, so a test could potentially resolve a dylib to a different copy than cargo test would. (Cargo swapped the two in 1.93.)

Fixed

• Nextest now computes the dynamic library search path correctly under build directory layout v2, which became the default on nightly Rust on 2026-07-30. Previously, tests that linked against a dylib dependency failed to start because the dynamic library could not be found.
• When Cargo's build.build-dir is configured, nextest now adds the Cargo artifact directory (where final artifacts like binaries and dynamic libraries are uplifted to) instead of the build directory (for intermediate artifacts) to the dynamic library search path. This matches Cargo's behavior.
• Nextest now detects the base output directory for test binaries built from [[example]] targets, which Cargo places in examples rather than deps. Previously, a run restricted to examples didn't add anything to the dynamic library search path, so an example test linking against a dylib failed to start.
• While creating an archive with a filterset, nextest now always includes dynamic libraries in the archive, even those from packages whose test binaries are all filtered out. Dynamic libraries are on the library search path and may be loaded by tests in other packages. Binaries exposed via CARGO_BIN_EXE_<name> are still filtered out if no test binaries from that package are selected. (#​3516)
• The "Archiving" message now counts non-test binaries correctly. Previously, nextest counted the number of packages containing non-test binaries rather than the number of binaries. (#​3515)

v0.9.141: cargo-nextest 0.9.141

Compare Source

Added

• A new junit.report-skipped configuration setting controls which skipped tests are emitted in the JUnit XML report as <testcase> elements with a <skipped> child. (#​885)

  Thanks to liangfu for your first contribution!

• While listing tests, nextest now shows a progress bar if listing takes longer than 2 seconds. Listing is usually fast, but can be slow in some environments, such as with antivirus software that scans each test binary before it runs. (#​3471)

• The binaries metadata (used by archives and --binaries-metadata) now records whether Cargo built each non-test binary for the host or the target platform. Future versions of nextest will use this to configure environment variables correctly in cross-compilation scenarios. (#​3520)

Changed

• Nextest now orders the dynamic library search path the way current versions of Cargo do, with the Cargo artifact directory ahead of the deps directory. Previously the two were reversed, so a test could potentially resolve a dylib to a different copy than cargo test would. (Cargo swapped the two in 1.93.)

Fixed

• Nextest now computes the dynamic library search path correctly under build directory layout v2, which became the default on nightly Rust on 2026-07-30. Previously, tests that linked against a dylib dependency failed to start because the dynamic library could not be found.
• When Cargo's build.build-dir is configured, nextest now adds the Cargo artifact directory (where final artifacts like binaries and dynamic libraries are uplifted to) instead of the build directory (for intermediate artifacts) to the dynamic library search path. This matches Cargo's behavior.
• Nextest now detects the base output directory for test binaries built from [[example]] targets, which Cargo places in examples rather than deps. Previously, a run restricted to examples didn't add anything to the dynamic library search path, so an example test linking against a dylib failed to start.
• While creating an archive with a filterset, nextest now always includes dynamic libraries in the archive, even those from packages whose test binaries are all filtered out. Dynamic libraries are on the library search path and may be loaded by tests in other packages. Binaries exposed via CARGO_BIN_EXE_<name> are still filtered out if no test binaries from that package are selected. (#​3516)
• The "Archiving" message now counts non-test binaries correctly. Previously, nextest counted the number of packages containing non-test binaries rather than the number of binaries. (#​3515)

---

Configuration

📅 Schedule: (in timezone UTC)

• Branch creation
  • "on sunday"
• 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.