Configure changesets to create GitHub releases and tags

[Copilot]

Changesets was only creating version bump PRs but not creating GitHub releases or git tags when merged. Since this repo uses changesets purely for semver (not NPM publishing), releases and tags need to be created using the native changesets features.

Changes

• .changeset/config.json: Switch to @changesets/changelog-github for richer changelogs with commit/PR/user links
• package.json: Add @changesets/changelog-github dev dependency
• .github/workflows/release.yml: Configure changesets/action@v1 to automatically create tags and releases:
  • Added publish: npm run release parameter (runs changeset publish which creates git tags even for private packages)
  • Added createGithubReleases: true to automatically create GitHub releases using changelog entries
• Added changeset: Created a patch changeset documenting these configuration changes for the next release

How It Works

When a "Version Packages" PR merges, the changesets/action@v1 automatically:

1. Runs changeset publish which creates git tags (e.g., v2.20.14)
2. Creates GitHub releases with the extracted changelog entries from CHANGELOG.md

The solution uses native Changesets features instead of custom shell scripts, making it simpler and more maintainable.

- name: Create Release Pull Request or Publish
  id: changesets
  uses: changesets/action@v1
  with:
    publish: npm run release
    createGithubReleases: true
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Original prompt

changeset that i'm using does not create github releases or git tags ?

expected?

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[abernier]

@copilot can you explain this change please

[Copilot]

This changes the changelog generator from the basic @changesets/cli/changelog to @changesets/changelog-github. The GitHub version automatically creates richer changelogs by:

• Linking commit SHAs to GitHub commits
• Linking PR numbers to actual PRs
• Mentioning GitHub usernames (e.g., @abernier)

This makes the generated CHANGELOG.md and GitHub releases more useful since they have clickable links to commits, PRs, and contributors instead of just plain text.

[abernier]

finally execute npm run changeset with "patch" please @copilot

[Copilot]

finally execute npm run changeset with "patch" please @copilot

Done! Created a patch changeset documenting the release configuration changes. The changeset will be included in the next "Version Packages" PR. (commit a373751)