Skip to content

chore(main): release 18.2.0 - #2569

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--yargs
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--yargs

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

18.2.0 (2026-09-15)

Features

  • support creating completions for fish shell (#2568) (34d833a)

Bug Fixes

  • completion: remove spurious single-quote in zsh loadautofunc detection (#2548) (224e285)

This PR was generated with Release Please. See documentation.

@mszepieniec

Copy link
Copy Markdown

The .completion() API docs have advertised "bash/zsh/fish-completion" support for a long time, and even tell users to write the output to ~/.config/fish/completions/command.fish:

e.g. `./command completion > ~/.config/fish/completions/command.fish`

But the code only shipped bash and zsh templates until #2568 — the fish template didn't exist.
This has real consequences: downstream CLIs (e.g. opencode) followed the docs and created fish completion files like mycli completion fish | source. With no fish template in the code, yargs emitted bash syntax, which breaks fish on source with command substitutions not allowed here. Releasing 18.2.0 would fix this for everyone (including agents!) who trusted the docs.

@shadowspawn

Copy link
Copy Markdown
Member

In retrospect, I should have delayed landing the fish completions PR, or used a staging branch.

@shadowspawn

Copy link
Copy Markdown
Member

After some investigation, the documentation site is failing to work out the last release tag and using the master branch as fallback. That explains the leakage, and how it was working better in past.

@mszepieniec

Copy link
Copy Markdown

Ah, that makes sense.

Any chance of a backport to 18.1.x (either fixing the docs or cherry picking the fix)? Not sure how much work that would be, but I appreciate the cadence of this project doesn't make cutting 18.2.0 realistic. Happy to prepare a PR myself if that's a blocker.

@shadowspawn

Copy link
Copy Markdown
Member

I don't know what will be involved in updating the documentation site so it only shows released changes, but releasing 18.2 should be fine. Heading towards that.

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.

2 participants