Skip to content

docs: clarify OpenCode V2 beta release flow - #34

Open
CasualDeveloper wants to merge 1 commit into
otto-assistant:betafrom
CasualDeveloper:docs/clarify-opencode-v2-beta-release
Open

docs: clarify OpenCode V2 beta release flow#34
CasualDeveloper wants to merge 1 commit into
otto-assistant:betafrom
CasualDeveloper:docs/clarify-opencode-v2-beta-release

Conversation

@CasualDeveloper

Copy link
Copy Markdown
Contributor

Summary

Follow-up to the non-blocking observations in the PR #33 review.

  • Document that each OpenCode V2 beta release requires a reviewed X.Y.Z-beta.N version bump before dispatching the workflow.
  • Clarify that the release workflow publishes the exact reviewed version and never creates version commits.
  • Explain why the constants regression test intentionally launches a fresh Bun process through process.execPath.

The permissive numeric forms accepted by Number() remain unchanged because strict decimal-only configuration is not currently required.

Verification

  • npm run verify
  • V1 smoke suite passes.
  • 40 V2/shared tests pass.
  • Typecheck, build, package validation, and OpenCode V2 loader smoke pass.
  • Release workflow YAML parses successfully.

Refs #31.

@CasualDeveloper
CasualDeveloper force-pushed the docs/clarify-opencode-v2-beta-release branch from 352035f to a4a9553 Compare September 3, 2026 16:32
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