Skip to content

[Completions] Bump command-signatures to 491864c0 (nx run fix) - #15114

Closed
warp-agent-staging[bot] wants to merge 1 commit into
masterfrom
factory/bump-command-signatures-nx-graph-fix
Closed

[Completions] Bump command-signatures to 491864c0 (nx run fix)#15114
warp-agent-staging[bot] wants to merge 1 commit into
masterfrom
factory/bump-command-signatures-nx-graph-fix

Conversation

@warp-agent-staging

@warp-agent-staging warp-agent-staging Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Description

Bumps the warp-command-signatures pin to pick up the fix for nx run <TAB> completions producing no suggestions (APP-5384 / #4691). command-signatures#335 has merged (squash commit 491864c0f695a32b77bef0942fe0f6cb54cb1567 on main), and this PR now points directly at that commit — the workspace_targets generator now uses nx graph --file=stdout instead of the broken --print/tmpfile fallback chain.

This repo pins command-signatures by commit rev (not a published version), so the fix does not reach users until this pin is bumped — that's the only purpose of this PR.

Linked Issue

Testing

No warp source was changed, only the command-signatures dependency pin. Verified:

  • cargo metadata --locked --no-deps — passes (lockfile is internally consistent for the manifest, no further resolution needed).

  • cargo check -p warp_completer --locked (the crate that consumes warp-command-signatures) — fetches commit 491864c0 and compiles cleanly.

  • Diff is minimal: Cargo.toml's rev field plus the two matching source = "git+...?rev=..." lines in Cargo.lock for warp-command-signatures/warp-completion-metadata — no unrelated dependency edges.

  • The underlying generator fix was verified against real Nx workspaces on nx@20.3.0 and nx@23.1.1 in command-signatures#335 — see that PR for the transcript.

  • I have manually tested my changes locally with ./script/run (not applicable: dependency-pin-only change with no warp source changes; verified via cargo check --locked instead, see above)

Agent Mode

  • Warp Agent Mode - This PR was created via Warp's AI Agent Mode

CHANGELOG-BUG-FIX: Fixed nx run <TAB> completions producing no suggestions on Nx versions prior to 21.6.

@warp-agent-staging

Copy link
Copy Markdown
Contributor Author

This PR was generated with Warp.

View run View conversation

@warp-agent-staging
warp-agent-staging Bot force-pushed the factory/bump-command-signatures-nx-graph-fix branch from 43cca55 to 3d12b54 Compare August 14, 2026 00:02
Points at warpdotdev/command-signatures#335 (merged), which fixes
`nx run <TAB>` completions (APP-5384 / #4691) by
switching the workspace_targets generator from the broken
`nx graph --print` / tmpfile fallback chain to `nx graph --file=stdout`.

Co-Authored-By: Warp Agent <agent@warp.dev>
@warp-agent-staging
warp-agent-staging Bot force-pushed the factory/bump-command-signatures-nx-graph-fix branch from 3d12b54 to ca1f10e Compare August 14, 2026 00:12
@warp-agent-staging warp-agent-staging Bot changed the title [Completions] Bump command-signatures to d1a508f9 (nx run fix) [BLOCKED on command-signatures#335] [Completions] Bump command-signatures to 491864c0 (nx run fix) Aug 14, 2026
@warp-agent-staging
warp-agent-staging Bot marked this pull request as ready for review August 14, 2026 00:14
@warp-agent-staging

Copy link
Copy Markdown
Contributor Author

Closing as superseded. #15109 bumped the pin to 15debaeb, which is 3 commits ahead of the 491864c0 this PR pins, so the nx --file=stdout fix from warpdotdev/command-signatures#335 is already on master and shipping.

Merging this now would move the pin backwards and revert the kubectl context forwarding that came with #15109.

Responding as wilson: Open session · View factory task

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.

1 participant