[Completions] Bump command-signatures to d79e09c (paru v2.1.0 CLI reconciliation) - #15159
Merged
Merged
Conversation
Updates warp-command-signatures to d79e09c43b64eb8e55a81fec088423aeba6a48cd. ### Merged PRs - Reconcile paru.json with the current paru v2.1.0 CLI (warpdotdev/command-signatures#337) ## Changelog Entries for Stable CHANGELOG-IMPROVEMENT: Corrected `paru` completions to match the current paru v2.1.0 CLI. Co-Authored-By: Warp Agent <agent@warp.dev>
acarl005
approved these changes
Aug 14, 2026
acarl005
enabled auto-merge (squash)
August 14, 2026 18:31
iamwavecut
pushed a commit
to iamwavecut/warp
that referenced
this pull request
Aug 15, 2026
…onciliation) (warpdotdev#15159) ## Description Bumps the `warp-command-signatures` git dependency to `d79e09c43b64eb8e55a81fec088423aeba6a48cd`, the current `main` of `warpdotdev/command-signatures`. This brings in warpdotdev/command-signatures#337, which reconciles `paru.json` against the real paru v2.1.0 CLI (audited against paru's own argument parser source, not just `--help`/the man page). `yay`/`paru` completions themselves already shipped in the prior pin bump (warpdotdev#15109); this is a spec correction on top — `paru` completions now describe options, operations, and argument types that match what paru v2.1.0 actually accepts, instead of the stale surface reflected by paru's shipped fish-completion script. Tracked by APP-5390. ## Linked Issue - [x] N/A — this is a dependency pin bump following on from warpdotdev#5177, not a new implementation against a tracked issue. ## Testing This is a data-only dependency bump (JSON completion spec changes in the upstream repo; no Rust code changed there between the old and new pin). Verified via: - `git diff <old-rev> <new-rev> --stat` in `command-signatures`, confirming the only change between the two pins is `command-signatures/json/paru.json`. - `cargo metadata --locked --format-version 1` in this repo, which succeeds with the new rev and confirms `Cargo.lock` is fully consistent with `Cargo.toml` (no other dependency drift). - [ ] I have manually tested my changes locally with `./script/run` Not manually tested end-to-end in a running Warp session (no computer-use/GUI access available). The underlying spec change was verified in warpdotdev/command-signatures#337 by building `paru` from the AUR in a container and checking its output against the new spec. ## Agent Mode - [x] Warp Agent Mode - This PR was created via Warp's AI Agent Mode <!-- CHANGELOG-IMPROVEMENT: Corrected `paru` completions to match the current paru v2.1.0 CLI. --> Co-authored-by: warp-agent-staging[bot] <240773466+warp-agent-staging[bot]@users.noreply.github.com> Co-authored-by: Warp Agent <agent@warp.dev>
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
1 participant
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.
Description
Bumps the
warp-command-signaturesgit dependency tod79e09c43b64eb8e55a81fec088423aeba6a48cd, the currentmainofwarpdotdev/command-signatures.This brings in warpdotdev/command-signatures#337, which reconciles
paru.jsonagainst the real paru v2.1.0 CLI (audited against paru's own argument parser source, not just--help/the man page).yay/parucompletions themselves already shipped in the prior pin bump (#15109); this is a spec correction on top —parucompletions now describe options, operations, and argument types that match what paru v2.1.0 actually accepts, instead of the stale surface reflected by paru's shipped fish-completion script.Tracked by APP-5390.
Linked Issue
Testing
This is a data-only dependency bump (JSON completion spec changes in the upstream repo; no Rust code changed there between the old and new pin). Verified via:
git diff <old-rev> <new-rev> --statincommand-signatures, confirming the only change between the two pins iscommand-signatures/json/paru.json.cargo metadata --locked --format-version 1in this repo, which succeeds with the new rev and confirmsCargo.lockis fully consistent withCargo.toml(no other dependency drift).I have manually tested my changes locally with
./script/runNot manually tested end-to-end in a running Warp session (no computer-use/GUI access available). The underlying spec change was verified in warpdotdev/command-signatures#337 by building
parufrom the AUR in a container and checking its output against the new spec.Agent Mode