Releasing

Releases are automated. You push a tag; GitHub Actions builds the extension, generates the changelog from the commits, and publishes the release.

Steps

1. Bump the version in both files (they must match the tag):

   • extension/manifest.json → "version"
   • extension/package.json → "version"

2. Commit, tag and push:

   git commit -am "chore(release): v0.1.2"   # Conventional Commits; no Co-Authored-By
   git tag v0.1.2
   git push origin main --tags

That's it. The release workflow then:

• verifies the tag matches manifest.json (fails loudly if not),
• runs lint + build,
• packages extension/dist into kimtos-v0.1.2.zip,
• writes release notes from the commits since the previous tag, and
• publishes the GitHub Release with the zip attached.

The in-app Release notes dialog fetches from GitHub, so it updates itself — no code change needed.

Notes

• Tag format is vMAJOR.MINOR.PATCH (e.g. v0.1.2).
• The changelog is built from commit subjects, so write clear ones.
• To publish to the Chrome Web Store, upload the kimtos-vX.Y.Z.zip asset from the GitHub Release to the Developer Dashboard.