Skip to content

Bump command-signatures to 4094b657 (yc CLI completions) - #14767

Merged
acarl005 merged 1 commit into
masterfrom
factory/app-5201-yc-command-signatures-bump
Aug 6, 2026
Merged

Bump command-signatures to 4094b657 (yc CLI completions)#14767
acarl005 merged 1 commit into
masterfrom
factory/app-5201-yc-command-signatures-bump

Conversation

@warp-agent-staging

Copy link
Copy Markdown
Contributor

Summary

Bumps the warp-command-signatures git dependency in warpdotdev/warp from 4990fa1d to 4094b657 (current warpdotdev/command-signatures:main), so the client picks up newly-merged completion specs.

Merged completion PRs now included:

This is the app-side half of APP-5201: the yc completion spec merged upstream in command-signatures#303, and this PR wires that spec into the app by advancing the embedded-signatures dependency. Only Cargo.toml (the rev) and Cargo.lock (the two git-source lines for warp-command-signatures / warp-completion-metadata) change.

The bump was produced by following the command-signatures repo's own update-command-spec-version skill (update the rev, sync Cargo.lock).

Verification

Testing-exempt category: dependency/version bump. Per factory-verification, a data-only dependency bump adds no regression test (a test would only assert data presence, not detect a logic defect); the yc spec itself is validated by command-signatures#303's own CI, which passed before merge.

App-side checks (run against the new rev, CARGO_TARGET_DIR redirected in the sandbox):

  • cargo check --locked -p warp_completer → success. --locked proves Cargo.lock is in sync with the new rev; the consuming crate compiles against the updated specs.
  • cargo test --locked -p warp_completer -- signatures:: → 12 passed / 0 failed. These load and validate the embedded command signatures (including the new yc spec).
  • Full cargo test --locked -p warp_completer → 138 passed / 25 failed. All 25 failures are a pre-existing, environmental test-harness issue unrelated to this change — Tried to check FeatureFlag::CloudEnvironments before feature flags were initialized (crates/warp_features/src/lib.rs) — not caused by the dependency bump.

No Rust source files change in this PR, so there is nothing for ./script/format or clippy to act on beyond the compile above.

User-facing note: the yc completion menu rendering from this exact spec was already demonstrated in a prior local GUI build against the spec branch; because this PR is a data-only dependency bump (no client code change), the GUI was not rebuilt for it. The rendering behavior is governed entirely by the upstream spec, which is validated by command-signatures#303.

CHANGELOG-IMPROVEMENT: Added inline command completions for the Yandex Cloud CLI (yc) and git worktree name suggestions.

Originating thread: https://warpdev.slack.com/archives/C0BDQDW8V5E/p1785974187380919

Updates the warp-command-signatures git dependency to pick up the merged
Yandex Cloud CLI (yc) completion spec (command-signatures#303) and the
git worktree name autocomplete suggestions (command-signatures#302).

Co-Authored-By: Warp <agent@warp.dev>
@cla-bot cla-bot Bot added the cla-signed label Aug 6, 2026
@warp-agent-staging warp-agent-staging Bot added the warpy-factory Label associated to the "Wob the Wuilder" factory on staging, also known as Warpy Factory. label Aug 6, 2026
@warp-agent-staging
warp-agent-staging Bot marked this pull request as ready for review August 6, 2026 01:58
@warp-agent-staging
warp-agent-staging Bot requested a review from acarl005 August 6, 2026 02:01
@acarl005
acarl005 enabled auto-merge (squash) August 6, 2026 02:06
@acarl005
acarl005 merged commit c553a67 into master Aug 6, 2026
48 checks passed
@acarl005
acarl005 deleted the factory/app-5201-yc-command-signatures-bump branch August 6, 2026 02:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed warpy-factory Label associated to the "Wob the Wuilder" factory on staging, also known as Warpy Factory.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants