Skip to content

chore(cli): remove the [BETA] labels from commands - #460

Merged
leggetter merged 1 commit into
mainfrom
chore/remove-beta-labels
Sep 27, 2026
Merged

leggetter merged 1 commit into
mainfrom
chore/remove-beta-labels

Conversation

@leggetter

Copy link
Copy Markdown
Collaborator

Removes the [BETA] label from every command that carried one.

Where Labelled since
Every Outpost command (hookdeck outpost …, including outpost mcp) v3.0.0
Event Gateway: connection, source, destination, event, request, attempt, issue, transformation, the four metrics commands, gateway mcp at least v2.0.0 — and never graduated

Each carried [BETA] in its short help and a feedback paragraph in its long help.

Why

A label that says don't rely on this yet, on commands we ship, document and announce as the headline of a major release, works against their use — and none of them carries the kind of risk a beta label exists to warn about. The Gateway labels show what happens to a beta with no exit criteria: it stays.

Change

  • gofmt -r 'ShortBeta(x) -> x' and 'LongBeta(x) -> x' unwrap every call, so only the labels change — 30 files, 102 lines swapped one for one.
  • ShortBeta, LongBeta and BetaFeedbackSuffix are removed.
  • The beta release channel — npm @beta, the hookdeck-beta formula — is untouched.

Verified

  • REFERENCE.md regenerated; generate-reference --check passes; 0 beta mentions.
  • All 135 commands' --help walked on a built binary: none mentions beta.
  • Both MCP servers with --allow-write (43 tools): no beta in any description, schema or server instructions.
  • Unit tests and go vet pass.

Outside this repository

REFERENCE.md also feeds the docs website, which needs regenerating to drop the labels there. The v3 changelog entry and blog post describe Outpost as beta, and live in the website repo.

Intended for v3.0.3.

🤖 Generated with Claude Code

https://claude.ai/code/session_012XtSQ2kfpcRXXqweskgXkH

Every Outpost command, and most Event Gateway commands -- connection, source,
destination, event, request, attempt, issue, transformation, the four metrics
commands and gateway mcp -- carried [BETA] in their short help and a feedback
paragraph in their long help. The Gateway ones have been labelled since at
least v2.0.0 and were never graduated.

A label that says "don't rely on this yet" on commands we ship, document and
announce as the headline of a major release works against their use, and none
of them carries the kind of risk a beta label should warn about.

gofmt -r unwraps every ShortBeta(x) and LongBeta(x) call to x, so only the
labels change; ShortBeta, LongBeta and BetaFeedbackSuffix are removed. The beta
*release* channel -- npm @beta, the hookdeck-beta formula -- is untouched.

REFERENCE.md is regenerated and passes --check. No command's --help, and no
MCP tool description or server instructions on either server, mentions beta.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012XtSQ2kfpcRXXqweskgXkH
@leggetter
leggetter merged commit 70405d4 into main Sep 27, 2026
14 checks passed
@leggetter
leggetter deleted the chore/remove-beta-labels branch September 27, 2026 13:45
chrisfinazzo pushed a commit to chrisfinazzo/hookdeck-cli that referenced this pull request Sep 28, 2026
hookdeck#460 removed [BETA] from every command. The Event Gateway commands had carried
it since at least v2.0.0, through several GA releases, because nothing said
what would take it off.

AGENTS.md now says the default is no label, and that a command, flag or MCP
tool is labelled beta only for operational risk the CLI cannot guard against,
a planned breaking change to its interface in the next minor release, or an
underlying API capability that is itself beta. Never for newness, low usage or
missing beta feedback. A justified label covers the narrowest thing at risk,
says what is unstable, records its exit criterion when it goes on, and is
reviewed at each minor release.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012XtSQ2kfpcRXXqweskgXkH
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant