chore(release): 2.1.0 - #215
Merged
Merged
Conversation
Version only. Everything this release contains is already on main, and the changelog entry landed in #214. Pushing this to main is what triggers publishing: publish.yml runs the full CI suite, then npm publish with provenance through Trusted Publishing, then cuts the v2.1.0 GitHub release. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
✅ Deploy Preview for react-xarrows ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe package version changes from ChangesPackage release
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
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.
Bumps
versionfrom 2.0.2 to 2.1.0. One line, nothing else touched.This is the trigger, not a preparation step. On merge,
publish.ymlfires on thepackage.jsonpath filter and:ci.ymlsuite as a required upstream jobnpm publishwith provenance, via Trusted Publishing, exercised for real for the first timev2.1.0GitHub release with generated notesnpm versions cannot be republished or unpublished after 72 hours (and unpublishing is disruptive well before that). Merge when you actually want 2.1.0 live.
Pre-flight already done
The publish workflow was dry-run on the #214 branch (run 31282647710).
verify / verifyresolved and passed,publishgated on it correctly, and the version guard skippednpm publish,Update npmandCreate GitHub releasebecause 2.0.2 was already live. So the wiring is proven; only the version guard's answer changes this time.Packed the 2.1.0 tarball locally:
Zero runtime dependencies in the published manifest, which is the headline change of the release.
What 2.1.0 contains
Already on main, fully described in
CHANGELOG.md. Summary:repeatCount="0"(repeatCount value of 0 prints a warning to the console #193, Fixed undefined headRef when using animation without arrowheads #181), dotted animation under StrictMode (Fix line SVG dotted animation in strict mode #174)If the publish fails
It fails closed. The version guard is idempotent and the release step checks for an existing tag, so re-running the workflow is safe.
🤖 Generated with Claude Code
Summary by CodeRabbit