Releases

Releases & Versioning

Loupe uses Semantic Versioning (MAJOR.MINOR.PATCH) and ships through GitHub Releases backed by git tags (vX.Y.Z).

• MAJOR — breaking changes to a public contract (SDK init config, API routes, MCP tools, DB schema).
• MINOR — backward-compatible features.
• PATCH — backward-compatible fixes.

Release process (the rule)

Every release must update the documentation. A version bump is not done until the changelog, wiki, and landing version reflect it.

1. Update CHANGELOG.md — move "Unreleased" entries under the new version + date.
2. Bump version in the affected package.json files.
3. Update the docs: this Changelog page, any changed feature/usage pages, and the landing page's version.
4. Commit, then tag: git tag vX.Y.Z && git push origin vX.Y.Z.
5. The release workflow (.github/workflows/release.yml) creates the GitHub Release from the changelog.

The full checklist lives in RELEASING.md. The rule is also encoded in the project's CLAUDE.md so AI agents follow it automatically.

History

See the Changelog and all releases.