Versioning & Release

Semantic versioning policy and release checklist for eslint-plugin-ai-guardrails maintainers.

This project uses Semantic Versioning (MAJOR.MINOR.PATCH).

Versioning Policy

Change Type	Version Bump	Examples
PATCH	`x.x.+1`	Bug fixes, docs-only fixes, non-breaking behavior adjustments
MINOR	`x.+1.0`	New rules, new options, backward-compatible enhancements
MAJOR	`+1.0.0`	Breaking changes to rule behavior, defaults, or public exports

Release Checklist

Ensure clean working tree

git status  # should be clean

Update `CHANGELOG.md`

Move items from [Unreleased] to a new version section and add the release date in YYYY-MM-DD format.

Run full quality checks

npm run clean
npm run build
npm test
npm pack --dry-run    # verify package contents

Bump version

npm version patch   # for bug fixes
npm version minor   # for new features
npm version major   # for breaking changes

Push tags and commits

git push --follow-tags

Publish to npm

npm publish

Create GitHub release

Go to Releases, create a release from the new tag, and copy the relevant CHANGELOG.md section as release notes.

Pre-publish Verification

Before every publish, verify the package contents:

npm pack --dry-run

Expected output should include dist/index.js, dist/rules/*.js, dist/cli.js, docs/**/*.md, README.md, and LICENSE. It should not include src/, tests/, node_modules/, or .stress-tests/.

Versioning & Release

On this page