Skip to content

chore(deps): update rust crate clap_complete_nushell to v4.6.1 - autoclosed - #444

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/clap_complete_nushell-4.x-lockfile
Closed

chore(deps): update rust crate clap_complete_nushell to v4.6.1 - autoclosed#444
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/clap_complete_nushell-4.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
clap_complete_nushell dependencies patch 4.6.04.6.1

Release Notes

clap-rs/clap (clap_complete_nushell)

v4.6.1

Compare Source

Fixes
  • (derive) Ensure rebuilds happen when an read env variable is changed

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 6am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot enabled auto-merge (squash) July 27, 2026 00:32
@repository-butler

Copy link
Copy Markdown
Contributor

Filter Verification Report

Changed Filters

No filter files changed in this PR.

All Filters Summary

✅ 151/151 test cases passed across 51 filters


Generated by tokf verify

mpecan added a commit that referenced this pull request Aug 7, 2026
Consolidates the six open renovate PRs into one branch, following the
precedent set by #435: one CI run and one review instead of six, and no
Cargo.lock conflict cascade from merging them one at a time.

All six are lockfile-only patch bumps within the existing Cargo.toml
constraints — no manifest changes:

| Crate                 | From → To       | Was  |
|-----------------------|-----------------|------|
| clap                  | 4.6.1 → 4.6.6   | #443 |
| clap_complete         | 4.6.7 → 4.6.9   | #447 |
| clap_complete_nushell | 4.6.0 → 4.6.1   | #444 |
| futures-util          | 0.3.32 → 0.3.33 | #445 |
| http-body-util        | 0.1.3 → 0.1.4   | #446 |
| keyring               | 4.1.5 → 4.1.6   | #448 |

clap_builder, clap_derive and the futures-core/io/macro/sink/task
family move alongside their parents; the resulting diff is exactly the
union of the six PRs with no extra crates picked up.

Supersedes #443, #444, #445, #446, #447, #448 — those PRs need closing
by hand, since GitHub's closing keywords apply to issues, not PRs.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
mpecan added a commit that referenced this pull request Aug 7, 2026
)

Batches the six open renovate PRs into one branch — one CI run, one
review, and no `Cargo.lock` conflict cascade from merging them
sequentially. Same approach as #435. Also clears two yanked crates found
while adding supply-chain checks.

## Taken — the six renovate PRs

| Crate | From → To | Was |
|---|---|---|
| clap | 4.6.1 → 4.6.6 | #443 |
| clap_complete | 4.6.7 → 4.6.9 | #447 |
| clap_complete_nushell | 4.6.0 → 4.6.1 | #444 |
| futures-util | 0.3.32 → 0.3.33 | #445 |
| http-body-util | 0.1.3 → 0.1.4 | #446 |
| keyring | 4.1.5 → 4.1.6 | #448 |

No `Cargo.toml` changes — every bump fits the existing constraints.
`clap_builder`, `clap_derive` and the
`futures-core`/`io`/`macro`/`sink`/`task` family move with their
parents; the diff is exactly the union of the six PRs, no extra crates
picked up.

## Also taken — two yanked crates (second commit)

| Crate | From → To | Reached via |
|---|---|---|
| spin | 0.9.8 → 0.9.9 | axum 0.8.9 → multer 3.1.0 |
| spin | 0.10.0 → 0.10.1 | aws-sdk-s3 1.137.0 → aws-smithy-checksums →
crc-fast 1.10.0 |

Both versions had been **yanked from crates.io**. Neither is reachable
from a direct dependency, so nothing surfaced them until `cargo deny
check advisories` went looking (that check is being added in a separate
PR). Each has a non-yanked successor inside the same semver range, so
this is lockfile-only too.

A yank is the mechanism by which a compromised release gets withdrawn,
so sitting on yanked versions is worth clearing regardless of why these
two were pulled.

## Why batch instead of merging the six

All six touch only `Cargo.lock`. Merging any one makes the other five
conflict, and renovate only rebases inside its schedule window (`before
6am on monday`) — so merging them one at a time would have spread across
several weeks.

## Why they were stuck

Renovate had already enabled squash auto-merge on all six on the day it
opened them. They sat at `mergeStateStatus: BLOCKED` / `reviewDecision:
REVIEW_REQUIRED`, because the `require-pr-approval` ruleset requires one
approving review and renovate cannot approve its own PR. Its bypass
actor is the admin repository role, which renovate does not hold. **The
`automerge: true` rule for cargo patch updates in
`.github/renovate.json` can therefore never fire** — every patch bump
keeps piling up until someone batches it by hand. Addressed in the
follow-up hardening PR.

The two red PRs (#443, #447) were not real failures — both were GitHub
Actions infrastructure flakes (`Failed to resolve action download info.
Error: Service Unavailable`). I re-ran them and they went green.

## Verification

- `cargo clippy --workspace --all-targets -- -D warnings` — clean
- `cargo test --workspace` — 2468 passed, 0 failed, 180 ignored
- `cargo deny check advisories bans sources` — passes with the spin fix;
failed on both yanked versions without it

## Superseded PRs

Supersedes #443, #444, #445, #446, #447, #448. GitHub's closing keywords
only auto-close issues, not PRs, so those six need closing by hand after
this merges — or renovate will autoclose them itself on its next
scheduled run (Monday before 6am).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
@renovate renovate Bot changed the title chore(deps): update rust crate clap_complete_nushell to v4.6.1 chore(deps): update rust crate clap_complete_nushell to v4.6.1 - autoclosed Aug 7, 2026
@renovate renovate Bot closed this Aug 7, 2026
auto-merge was automatically disabled August 7, 2026 15:32

Pull request was closed

@renovate
renovate Bot deleted the renovate/clap_complete_nushell-4.x-lockfile branch August 7, 2026 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants