releases-changesets

name	releases-changesets
description	Uses changesets for versioning and changelog; avoids manual version bumps; aligns with build/zip and workflow_dispatch. Use when cutting a release, adding a changeset, preparing for publish, or when touching version or changelog.

Releases and Versioning (changesets)

Rule

All user-facing or notable changes get a changeset in .changeset/. Do not edit package.json version manually for releases.

Adding a changeset

• Run pnpm changeset, or add a new .md file in .changeset/ with the standard format: semver type (major/minor/patch) and a short summary for the changelog.

Non-interactive automation

When automation must avoid interactive prompts:

1. Run pnpm changeset add --empty --message "<summary>".
2. Update the generated .changeset/*.md frontmatter to include the release bump, for example:
   • "amgiflol": patch
3. Validate before finalizing:
   • pnpm changeset status
   • relevant project checks used by the current task (for example pnpm check, pnpm lint).

Notes:

• --empty creates an empty frontmatter block by default (--- ---) and does not select patch/minor/major.
• --message only sets the summary text and does not set bump type.

Config

.changeset/config.json: changelog: "@changesets/cli/changelog", commit: false, baseBranch: "main".

Release steps

1. Build both targets: pnpm build:all
2. Create zips: pnpm zip:all
3. workflow_dispatch (e.g. issue #27) is the intended automation when available; document in README when in place.