ci(release): Add prerelease workflow support#44
Merged
Conversation
Allow the manual release workflow to compute beta, rc, and alpha prerelease versions from the current package version. This keeps preview builds distinct from the stable release line while preserving the normal patch, minor, and major flow. Mark scoped harness packages as public in Craft and package manifests so their first npm publishes use public access. Co-Authored-By: OpenAI Codex <codex@openai.com>
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
1 participant
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.
Add prerelease controls to the manual Release workflow so the existing bump input can produce beta, rc, or alpha versions from the current package version. Stable releases still use patch, minor, and major, while preview releases stay on a distinct npm prerelease line.
Version Calculation
Add a small release-version script for the cases the workflow needs: stable to prerelease, prerelease increments, and prerelease promotion back to stable.
Package Access
Mark the scoped harness packages as public in Craft and their package manifests so their first npm publishes use public access.
Validated with pnpm release:check, Biome lint on the version script, and focused version-calculation examples.