Skip to content

docs(readme): elevate Beta status + bump pin to 0.2.0-beta.4#23

Merged
caballeto merged 1 commit into
mainfrom
docs/readme-beta-status
May 6, 2026
Merged

docs(readme): elevate Beta status + bump pin to 0.2.0-beta.4#23
caballeto merged 1 commit into
mainfrom
docs/readme-beta-status

Conversation

@caballeto
Copy link
Copy Markdown
Member

Promotes the README's versioning paragraph to a proper Status: Beta section so users understand we are intentionally holding TF on the beta line while the other DevHelm surfaces (CLI, SDKs, MCP server) ship at 1.0.0 today. Adds a Beta status badge. Bumps the quickstart pin to the currently published 0.2.0-beta.4. No code changes.

Made with Cursor

Replace the inline versioning paragraph with a proper "Status: Beta"
section explaining what beta means in practice (safe for production,
fully supported, pin the exact pre-release version, track CHANGELOG).
Add a Beta status badge next to the Registry / godoc / license badges
so it's visible at a glance.

Bump the quickstart pin from `0.2.0-beta.1` to `0.2.0-beta.4` (the
currently published latest tag with the lenient response decoder).

Why we're holding TF on the beta line while the other DevHelm
surfaces (CLI, SDKs, MCP server) are at 1.0.0: a short soak window
to harden one defense-in-depth edge case (post-POST failure rollback
in the API client) before promoting to GA. Schema and on-disk state
format are stable and will not change before 1.0.0.

Co-authored-by: Cursor <cursoragent@cursor.com>
@caballeto caballeto merged commit ec1cbf4 into main May 6, 2026
6 checks passed
@caballeto caballeto deleted the docs/readme-beta-status branch May 6, 2026 19:24
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