HyperFrames publishes two release channels:Documentation Index
Fetch the complete documentation index at: https://hyperframes-docs-hyperframes-mcp.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
- Stable releases use versions like
0.4.24and publish to the npmlatestdist-tag. - Prereleases use versions like
0.4.24-alpha.1and publish to the npm dist-tag named by the prerelease suffix, such asalpha.
Branch policy
Use branch separation to decide what code is eligible for each release channel. Dist-tags only control npm install defaults; they do not remove code from a package.mainis stable/releasable. Anything merged tomainis eligible forlatest.release/v*branches are for stable patch releases and hotfixes.next,alpha,beta,rc,canary, andprerelease/*branches are for prerelease integration.
main.
Stable release
Stable releases must be reachable fromorigin/main or origin/release/v*.
Alpha release
Alpha releases must be reachable from a prerelease branch such asorigin/next or origin/alpha.
CI guardrails
The publish workflow validates release channel boundaries before publishing:- Stable versions must publish with
latest. - Prerelease versions must publish with the prerelease dist-tag, such as
alpha. - Stable tags must be reachable from
mainorrelease/v*. - Prerelease tags must be reachable from a prerelease branch.
- Merged
release/vX.Y.ZPRs publish stable releases only.