chore: prepare the 2.1.0 release - #214
Conversation
Removes the unmaintained banner from the README. It has been the first thing every reader saw since 2024 and it is no longer true. Adds the 2.1.0 changelog entry. CHANGELOG.md ships inside the tarball, so leaving it at 2.0.2 means the published package documents none of this work. The entry calls out the two changes that can affect a working setup even though the API is unchanged: the build target moved from ES5 to ES2015, and prop-types is gone so JavaScript users on React 18 and below lose dev-time prop warnings. Gates publishing on the full CI suite. publish.yml re-ran lint, type-check, test and build inline, which skipped exactly the checks that guard the tarball: format, the demo build and tests, attw, package contents and the entry-point smoke tests. It now calls ci.yml as a reusable workflow and keeps only the build step, which it still needs because it publishes from its own checkout. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
Warning Review limit reached
Next review available in: 12 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
Comment |
✅ Deploy Preview for react-xarrows ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
index.d.mts and index.d.cts were never verified even though the exports map points the per-condition types at them, and they are produced by a copy step in vite.config.mts that fails quietly. attw catches this indirectly; checking the files directly is one word. Anchors the greps. "package/lib/index.d.ts" also matches index.d.ts.map, so a sourcemap could stand in for the file it maps. No .d.ts.map is emitted today, which is what makes it worth closing now rather than after it bites. Adds a 15 minute timeout. The suite runs in about a minute, so anything near the limit is hung, and the six hour default is a long time to block a release. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
1 participant
Everything that should land before the version bump. No source changes, so the published behavior of the library is untouched by this PR.
README
Drops the "I'm no longer maintaining this project" banner. It sat above everything else and is no longer true. Replaced the
Help wantedsection with aProject statussection that says what is actually happening, and added the two new packaging facts to the feature list.CHANGELOG
CHANGELOG.mdis infiles, so it ships inside the tarball. It currently stops at 2.0.2, which means the published package documents none of the last week's work.The entry is explicit about the two things that can break a working setup even though no API changed:
node_modulesdown to ES5 now has to include react-xarrows in that pass.Contributor credit for #174 (@Reflejo) and #181 (@dthomasen).
publish.yml
This is the one worth a look. The publish job re-ran
lint,type-check,testandbuildinline. That is a subset ofci.ymlthat had already drifted: it skippedformat:check, the demo build and tests,attw, the package-contents check, and the entry-point and UMD smoke tests. Those are precisely the checks that catch a broken tarball, and 2.1.0 is the first release ever to go out through Trusted Publishing.publish.ymlnow callsci.ymlas a reusable workflow and depends on it. The only step kept inline isbuild, because the publish job publishes from its own checkout and needslib/present.Cost: CI runs twice on a version-bump push, once from
ci.yml's ownpush: maintrigger and once inside the publish run. They land in different concurrency groups so neither cancels the other.Also done outside this PR
refactor/drop-runtime-depsbranch.Left for after 2.1.0
#178 (
roundedCorners) is a real feature and conflicts with main.🤖 Generated with Claude Code