Release

Prepare and publish a release directly from main.

Overview

This workflow helps you:

1. Select/confirm the target version
2. Curate CHANGELOG.md entries manually for end users
3. Ensure package.json version matches the changelog
4. Create and push a release commit + tag
5. Trigger publish workflow
6. Update GitHub release notes and share a summary

Process

1) Sync and determine version

git checkout main
git pull origin main
cat package.json | grep '"version"'

Confirm the release version with the maintainer (patch/minor/major).

2) Curate changelog and version

• Edit CHANGELOG.md for the target version using human-friendly release notes.
• Ensure version headers use bracket format, e.g. ## [3.66.1].
• Update package.json version to the same value.

3) Commit and tag

git add CHANGELOG.md package.json package-lock.json
git commit -m "v<version> Release Notes"
git push origin main
git tag v<version>
git push origin v<version>

4) Trigger publish workflow

Tell the maintainer to run: https://github.com/cline/cline/actions/workflows/publish.yml

Use v<version> as the release tag.

5) Update GitHub release notes

After publish completes:

gh release view v<version> --json body --jq '.body'
gh release edit v<version> --notes "<final curated release notes>"

6) Final summary

Provide:

• Released version/tag
• Link to release page
• Summary of top end-user changes