chore(deps): update docker#187
Open
bootc-bot[bot] wants to merge 1 commit into
Open
Conversation
5f277bd to
887da86
Compare
Signed-off-by: bootc-bot[bot] <225049296+bootc-bot[bot]@users.noreply.github.com>
887da86 to
d4bee6f
Compare
This file contains hidden or 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
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:
0.11.13→0.11.14v1.33.1→v1.34.10.9.133→0.9.136nightly-2026-05-10→nightly-2026-05-17Release Notes
astral-sh/uv (astral-sh/uv)
v0.11.14Compare Source
Released on 2026-05-12.
Enhancements
top_level.txtentries in uninstall that are not valid Python identifiers (#19340)Bug fixes
.envfiles in parent process (#19343)uv treeshowing extra-conditional deps for packages required without extras (#19332)--no-build) during lock validation (#19366)block/goose (block/goose)
v1.34.1Compare Source
🔧 Improvements
v1.34.0Compare Source
✨ Features
🐛 Bug Fixes
🔧 Improvements
📚 Documentation
nextest-rs/nextest (nextest-rs/nextest)
v0.9.136: cargo-nextest 0.9.136Compare Source
Added
cargo nextest self schema user-config. (#3351)Changed
max-progress-runninguser-config setting no longer accepts numeric strings like"8"(an undocumented fallback). The supported values remain a non-negative integer (e.g.8) or"infinite". (#3350)v0.9.135: cargo-nextest 0.9.135Compare Source
Fixed an issue with a from-crates.io build.
v0.9.134: cargo-nextest 0.9.134Compare Source
Added
Nextest now provides a JSON Schema for repository configuration at
.config/nextest.toml, enabling validation and IDE autocompletion via the Tombi language server.Thanks ya7010 for your first contribution, and for maintaining Tombi!
(Note that the Taplo language server is not supported due to a crash bug. The schema has been tested to work with Tombi.)
For target triples that nextest doesn't have built-in information about, nextest now invokes
rustc --print=cfg --target=<triple>to resolve platform information before falling back to heuristic detection. This is particularly useful for custom builds of the Rust toolchain. (#3331)Thanks mhatzl for your first contribution!
Changed
User config platform overrides are now always evaluated against the build target: the platform nextest was compiled for. Previously, the build target was used in some cases and the host platform in others. (#3285)
In most cases the build target matches the host platform, but they can differ when, for example, running an
x86_64-unknown-linux-muslnextest binary on a glibc (-gnu) host. This change does not affect per-test overrides, which continue to be matched against the host or target platform of the tests being run.Fixed
cargo nextest store exportandcargo nextest store export-chrome-tracenow verify the store format version before exporting, matching the behavior ofcargo nextest replayand the rerun commands. (#3287)Configuration
📅 Schedule: (in timezone UTC)
🚦 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 has been generated by Mend Renovate.