Skip to content

RELEASE.md

Latest commit

 

History

History
26 lines (19 loc) · 945 Bytes

RELEASE.md

File metadata and controls

26 lines (19 loc) · 945 Bytes
Raw

Release Process

StellarHunts uses Semantic Versioning and tags to trigger releases.

Cutting a release

  1. Decide the next version: bump MAJOR for breaking changes, MINOR for new features, PATCH for bug fixes.
  2. Create and push the annotated tag: 
    git tag -a vX.Y.Z -m "Release vX.Y.Z"
git push origin vX.Y.Z
  3. The Release workflow will automatically:
    • Build the frontend, backend, and on-chain (Soroban) artifacts
    • Generate a release changelog from conventional-commit messages
    • Attach the compiled .wasm contract files to a GitHub Release

Conventional commits

Commit messages prefixed with feat:, fix:, docs:, refactor:, test:, ci:, chore:, or style: are grouped under those headings in the release notes.

Hotfixes

For urgent patches, branch from the latest tag, fix, and tag a new PATCH version.