chore: production deploy#5296
Merged
Merged
Conversation
#5294) Fixes two issues in the release workflow that affect cross-platform compatibility and npm publishing: - **Smoke test shell**: Added explicit `shell: bash` to the smoke test step. The Windows runner defaults to PowerShell, which treats `${VERSION}` and `${NPM_TAG}` as empty variables (PowerShell uses `$env:VAR` syntax). This ensures consistent variable expansion across the ubuntu/macos/windows matrix. - **NPM tag quoting**: Removed unnecessary double-quoting of the `${NPM_TAG}` variable in the publish step (`""${NPM_TAG}""` → `"${NPM_TAG}"`). The extra quotes were being passed literally to the script, causing incorrect tag values. https://claude.ai/code/session_018LbJcjCcwYkz86cN5Qw19s Co-authored-by: Claude <noreply@anthropic.com>
## TL;DR hide legacy subcommands from help output when the go cli marks them hidden, while keeping them callable ## prob the legacy ts cli still showed a few subcommands in `--help` that the go cli explicitly marks as hidden: - `branches disable` - `db branch` - `db remote` - `db test` this happened because the existing hidden help mechanism only covered flags, not subcommands change extends the same pattern to hidden subcommands and annotates the affected parent commands accordingly execution is unchanged, so the subcommands remain callable directly ## ref: - extends #5278
avallete
approved these changes
May 19, 2026
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
2 participants
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.
Fixes two issues in the release workflow that affect cross-platform
compatibility and npm publishing:
Smoke test shell: Added explicit
shell: bashto the smoke teststep. The Windows runner defaults to PowerShell, which treats
${VERSION}and${NPM_TAG}as empty variables (PowerShell uses$env:VARsyntax). This ensures consistent variable expansion acrossthe ubuntu/macos/windows matrix.
NPM tag quoting: Removed unnecessary double-quoting of the
${NPM_TAG}variable in the publish step (""${NPM_TAG}""→"${NPM_TAG}"). The extra quotes were being passed literally to thescript, causing incorrect tag values.
https://claude.ai/code/session_018LbJcjCcwYkz86cN5Qw19s
Co-authored-by: Claude noreply@anthropic.com