Releasing

Releases use annotated (ideally GPG-signed) git tags following semver:

vX.Y.Z — immutable per-release tag (e.g. v1.0.12), never moved once pushed.
v1 — floating major tag that always points at the latest v1.Y.Z release. Consumers pin to it (uses: ForAllSecure/mcode-action@v1), so moving it after each release lets them pick up updates automatically.

v1-dev is a stale, unrelated legacy tag — ignore it during releases.

Steps

Directly on main (no separate branch or PR), commit the bump of version in package.json to the new release version and push it:
```
git commit -am "Prepare v1.0.12 release" -m "* Bump package.json version to 1.0.12"
git push origin main
```

On that commit, tag and push the release:

git tag -a v1.0.12 -m "Release v1.0.12" -s
git push origin v1.0.12

Move the floating major tag to the same commit and force-push:

git tag -fa v1 -m "Update v1 tag to v1.0.12" -s
git push origin v1 --force