ci: add automated release pipeline for npm

[zacowan]

Context

The release process for this repository only released changes to GitHub, which introduced a few problems:

• npm versions and GitHub Release versions could drift out of sync
• The font files in packages/next/dist/fonts were manually maintained and not updated as part of the build process, meaning it was possible to forget to update the font files in the npm package even if the font files in the github release were accurate

Solution

Consolidated the release pipeline into a single workflow controlled entirely by changesets:

• Changesets-driven releases: Changesets now handles both npm publishing and GitHub Release creation. The font zip is uploaded to the GitHub release that Changesets creates
• Automated font copying: Added copy-npm-fonts target to the Makefile that copies built ttf/woff2 files into packages/next/dist/fonts/ as part of make build, with necessary renames to match existing naming conventions
• Zip generation in build: Moved release zip creation into the Makefile (create-release-zip target) so it's generated alongside fonts, rather than as part of the github action
• Documentation: Added CONTRIBUTING.md explaining the release process and how to use changesets

This also introduces some small QoL changes to the repo:

• We now use corepack to manage the package manager (in this case, pnpm) version
• We now have a .nvmrc file to ensure we use a consistent version of Node.js

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
v0-vercel-geist-font	Ready	Preview, Comment, Open in v0	Feb 4, 2026 8:36pm

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​next@​14.0.1 ⏵ 16.1.1	+4	+57	-3	+47
	npm/​@​changesets/​cli@​2.29.8

View full report