chore: switch release flow to Changesets#32
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces the manual
## Unreleasedsection in rootCHANGELOG.mdwith Changesets. Each PR that touches a published package now drops a.changeset/*.mdfile;pnpm versionconsumes them into per-package CHANGELOGs and bumps versions;pnpm releasebuilds and publishes.Why: parallel PRs no longer collide on the Unreleased section (today every concurrent feature branch had to rebase the same lines), and releases stop being a manual ritual of editing
CHANGELOG.md+ bumping everypackage.jsonby hand.What's in the PR
pnpm add -Dw @changesets/cli+pnpm changeset init).fixed: [["@formhaus/core", "@formhaus/react", "@formhaus/vue"]]— these three keep matching versions, as they have historically.ignore: ["@formhaus/figma"]— Figma plugin isn't on npm.access: "public"— npm scope is@formhaus/*, needs explicit public access.@formhaus/figmaasprivate: true— it isn't published to npm (per README, install as local Figma plugin).lint:packagesandcheck:typesalready excluded it. Adding the field makes that explicit and preventspnpm publishfrom ever picking it up.package.jsonscripts:pnpm changeset(record),pnpm version(apply),pnpm release(build + publish).CHANGELOG.md: replacedUnreleasedwith a one-screen note pointing to per-package CHANGELOGs and Releases. Historical entries preserved verbatim.CONTRIBUTING.md: updated step 5 from "add a Unreleased entry" to "runpnpm changeset". Added a Changesets section explaining the flow..changeset/ssr-server-snapshot.md— patch on@formhaus/react.changeset/datetime-field-type.md— minor on core/react/vue.changeset/autocomplete-field-type.md— minor on core/react/vueVerifying
pnpm changeset statusshows the next release will bump core/react/vue from 0.3.1 to 0.4.0 (minor wins over patch).When you're ready to cut the release:
(Or set up a Changesets release GitHub Action later — happy to add if you want.)
Verifying tests
pnpm install --frozen-lockfile,pnpm -r run build,pnpm -r run testall green (179 tests: 136 core + 22 react + 12 vue + 15 figma).