chore: adding changesets to make releases easier

[Kylejeong2]

what

MCP server releases to npm registry should be easier and happen more often.

[greptile-apps]

Greptile Summary

This PR introduces Changesets tooling to modernize the release workflow for the MCP server package. The changes replace a manual, GitHub release-triggered publishing system with an automated, continuous integration approach.

The key modifications include:

• Package.json updates: Added three new npm scripts (changeset, version:packages, release) and the @changesets/cli dev dependency. Also added publishConfig with public access for scoped package publishing.

• New automated workflow: Added .github/workflows/release.yml that triggers on pushes to main and uses the changesets/action to either create release PRs for version bumping or publish packages directly to npm.

• Legacy workflow removal: Removed the old .github/workflows/publish.yml that required manual GitHub release creation.

This change integrates well with the existing codebase structure. The MCP server is already set up as a publishable npm package with proper TypeScript compilation, ESLint configuration, and build processes. Changesets builds upon this foundation by providing automated semantic versioning, changelog generation, and publishing capabilities. The workflow leverages the existing pnpm setup and build scripts, making it a natural extension of the current development workflow.

The approach follows modern npm package publishing practices, particularly beneficial for projects that need frequent releases and clear version management. By automating the release process, it reduces the friction for contributors to ship updates and ensures consistent versioning practices.

Confidence score: 4/5

• This PR is safe to merge with only minor considerations around workflow cleanup
• Score reflects well-established tooling and straightforward configuration changes, with only minor cleanup needed
• Pay close attention to the empty publish.yml file which should be deleted entirely rather than left empty

Context used:

Context - We enforce linting and prettier at the CI level, so no code style comments that aren't obvious. (link)

_{3 files reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}