Skip to content

release-policy.md

Latest commit

 

History

History
35 lines (24 loc) · 1.34 KB

release-policy.md

File metadata and controls

35 lines (24 loc) · 1.34 KB

Release Policy

This policy defines how LifeOS cuts repeatable releases.

Deprecation timing and removal guarantees are defined in docs/platform/deprecation.md.

Versioning

LifeOS uses Semantic Versioning for tagged releases.

  • patch: bug fixes, docs corrections, internal hardening with no behavior break
  • minor: new stable capabilities and additive interfaces
  • major: breaking behavior or contract changes

Changesets Workflow

  1. Add a changeset entry for every user-visible change.
  2. Merge PRs into main with pending changesets.
  3. The Release Versioning workflow runs on main, executes pnpm run validate, and opens or updates the version PR only after that full gate passes.
  4. Merge the version PR to update package versions and CHANGELOG.md.
  5. Tag the merged release commit (example: v0.3.0) and push the tag.
  6. The Release Tag workflow publishes the GitHub release from that tag.

Operator Checklist Before Tag

  • pnpm run validate passes locally and in CI
  • release-impacting docs are updated
  • CHANGELOG.md entries are accurate and complete
  • the version PR has been merged to main
  • the tagged release commit is on main and clean (git status -sb)

Current Default

  • GitHub release tags + changelog are enabled.
  • npm publishing is intentionally disabled for this cycle.