[ci] release#144
Merged
Merged
Conversation
commit: |
bombshell-bot
Bot
force-pushed
the
changeset-release/main
branch
from
July 20, 2026 11:27
f9ed7e8 to
3b69b9b
Compare
bombshell-bot
Bot
force-pushed
the
changeset-release/main
branch
from
July 20, 2026 11:44
3b69b9b to
3369415
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@bomb.sh/tab@0.0.21
Patch Changes
7462e1a: fix(fish): pass multi-segment CLI paths as separate arguments
In fish, completing a package-manager-delegated CLI with more than one path segment (e.g.
pnpm <cli> <subcommand> --<TAB>) returned nothing and fell back to the package manager's own flags. The generated fish script built the request withstring join ' '+eval, and because fish does not expand bare(...)command substitution inside double quotes, the whole path collapsed into a single token on re-parse. The template now invokes the backend directly with fish list expansion, so every segment reaches the completion backend as its own argument. zsh and bash already quoted each argument individually; PowerShell was audited and quotes each token beforeInvoke-Expression, so it is unaffected.2005004: perf: make package-manager-delegated completions much faster
tab <pm> complete -- <cli> ...(thepnpm <cli> <TAB>path, plus the npm/yarn/bun equivalents) no longer parses<pm> --helpon the delegation path and launches the target CLI at most once instead of twice. On a real project this drops the tab overhead from ~0.5s to a single CLI launch.Also fixes a correctness gap where a CLI installed only locally (reachable via
<pm> <cli>but not onPATH) could be detected yet return no completions: the fetch now tries the CLI directly first and falls back to running it through the package manager. The parsed<pm> --helpcommand tree is cached on disk (fingerprinted by the resolved executable, with a TTL) so package-manager-self completions stay fast too.