Repository navigation
chore: add release tooling and drop invariant and shallowequal - #278
Merged
Merged
Conversation
Releases were manual: npm has 3.0.0, but the newest GitHub release is 0.2.0 and only v3.0.0 has a tag. `pnpm release <bump>` now moves the [Unreleased] changelog entries into a version section and opens a release pull request. Merging it runs publish.yml, which publishes the version through npm trusted publishing if npm doesn't have it, then creates the GitHub release and tag from the changelog. Pull requests from forks never ran CI; they do now, while branches in this repository keep running it on push only. Dependabot proposes npm and GitHub Actions updates weekly. invariant and shallowequal are replaced by a small helper and PureComponent. The README's React 19 section no longer says server code works unchanged, and CHANGELOG.md covers everything since 3.0.0.
staylor
force-pushed
the
modernize-release-tooling
branch
from
November 11, 2026 20:34
bc41243 to
531ad40
Compare
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.
Problem
Releasing was manual and left no trail: npm has 3.0.0, but the newest GitHub release is 0.2.0 from 2018, and
v3.0.0is the only version tag. Pull requests from forks got no CI at all (#259 only showed a stale CircleCI check). The README said React 19 needs no code changes, although<HelmetProvider>doesn't fill incontextthere.invariantandshallowequalwere runtime dependencies for what a five-line helper andPureComponentdo.Fix
pnpm release <major|minor|patch|x.y.z>moves the[Unreleased]entries in CHANGELOG.md into a version section, bumpspackage.jsonand opens arelease/v<version>PR.--dry-runprints the notes.publish.yml. If npm doesn't have the version, it runs tsc and the unit tests and publishes through npm trusted publishing (provenance included), then creates the GitHub release and tag with the changelog section as notes. Merging this PR publishes nothing, since 3.0.0 is on npm, and creates the missing v3.0.0 release.exportsincludes./package.jsonagain, and the README gains Installation and Releasing sections and accurate React 19 server caveats.[Unreleased]covers everything merged since 3.0.0.Notes
Before merging the first release PR, add the trusted publisher on npmjs.com: GitHub Actions,
staylor/react-helmet-async/publish.yml, withnpm publishallowed (new configurations only allownpm stage publishby default). A configuration that isn't used within 2 days expires.Tests
release-helpers.test.tscovers version bumps and the changelog rewrite. In a sandbox clone with a stubbedgh,pnpm release minorpushed a one-commitrelease/v3.1.0that changes only the version, the heading and the compare links.releasefor 3.0.0 andpublishplusreleasefor an unpublished version; actionlint passes.lib/differs frommainonly by the dependency swap, and the packed file list is unchanged.