Renovate batch, verified 2026-09-30 #22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/batch-2026-09-30"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Renovate batch prepared and verified on 2026-09-30. It carries the Renovate branches below in one branch, so the default branch gets one CI run and one image build instead of one per PR. The individual PRs are left open; nothing was closed.
Base:
mainat3a36d36b12.Batch head:
2971c57f60.Included, merged in this order with
git merge --no-ff. Each line gives the head commit's own subject, which is what the branch actually carries:renovate/rustls-pki-types-1.x-lockfileat267acf90ce: Update Rust crate rustls-pki-types to v1.15.1renovate/uuid-1.x-lockfileatfb0db7b6a4: Update Rust crate uuid to v1.26.1renovate/tokio-1.x-lockfileat4911cfb0cb: Update Rust crate tokio to v1.53.1Skipped:
Gate. This repo's only CI workflow is gitleaks, and it was run here: gitleaks 8.21.2 (the same pinned binary and checksum as the workflow),
gitleaks detect --source . --no-banner --redact --verboseon this clone: 0 findings, 35 commits scanned. There is no Rust step in its CI. The Rust gate, run locally on the batch tree with rustc 1.98.1:3a36d36b12(same 30 diffs), so pre-existing.carrier; the identical error set appears on main at3a36d36b12, so pre-existing. Clippy stops at the first crate that fails, so crates that depend on it were not linted on either side.Pre-existing failures carried:
3a36d36b12.carrier, identical on main at3a36d36b12.