Releases

Version scheme

ashlr uses semantic versioning. Given the plugin's role as a tool layer, the rules are:

• Patch (1.x.Y) — bug fixes, documentation, no API changes
• Minor (1.Y.0) — new tools, new skills, backward-compatible schema changes
• Major (Y.0.0) — breaking changes to tool input schemas or stats schema

Release checklist

1. Update CHANGELOG.md with the new version section
2. Run bun run test — all tests must pass
3. Run bun run typecheck — zero type errors
4. Bump version in package.json
5. Commit: git commit -m "chore: release vX.Y.Z"
6. Tag: git tag vX.Y.Z
7. Push: git push && git push --tags
8. The GitHub Actions release.yml workflow creates the GitHub release and available build assets on tag push
9. Publish the package to npm manually using the command below; verify the registry version after publication

Publishing manually

The GitHub release workflow does not publish to npm. After the release checks pass:

npm publish --access public

Requires an authenticated npm account with permission to publish ashlr-plugin. If npm reports E401, complete interactive login before retrying; a GitHub release does not establish npm availability. Verify publication with npm view ashlr-plugin version dist-tags --json.

Changelog format

## vX.Y.Z — 2024-01-15
 
### Added
- ashlr__diff_semantic: AST-aware diff summarization
 
### Fixed
- ashlr__read: incorrect line count on Windows CRLF files
 
### Changed
- Stats schema bumped to v2 (auto-migrated on first run)

Deprecation policy

Tool input schema fields are deprecated for one minor version before removal. Deprecated fields are documented in the changelog and logged as warnings in the MCP server output.