chore(release): 2.2.1 - #91
Conversation
Prepared by scripts/prepare-release.mjs. Merging this PR (any merge method) triggers this workflow's PUBLISH mode, which tags, publishes to npm, and creates the GitHub release — nothing publishes until this merges.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
Included review availability: Your plan provides up to 10 included reviews per hour; 6 remain after this review. 📝 WalkthroughWalkthroughThe package version changed from 2.2.0 to 2.2.1. The changelog documents the release and the js-yaml CVE-2026-84375 dependency vulnerability fix. ChangesRelease metadata
Priority: ➖ Normal Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to The release metadata and dependency fix are aligned with the package being published, so no merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 6✅ Passed checks (6 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
asachs01
left a comment
There was a problem hiding this comment.
Code Review Summary — automated release PR
Verdict: Approve
Reviewed via gh pr diff. Changes are exactly what the title claims: a patch version bump (2.2.0 → 2.2.1) plus the standard package.json/package-lock.json/CHANGELOG.md triplet generated by semantic-release.
Checklist
- Correctness: version bumped consistently in
package.jsonandpackage-lock.json; CHANGELOG entry matches (js-yaml CVE-2026-84375 dependency fix referenced by commit). - Security: no hardcoded secrets/credentials introduced. This release itself is a security fix (resolves a known js-yaml CVE) — good.
- Code quality: no source changes, purely metadata/version files.
- Tests: N/A — no logic changed; CI (
Test (22)) is green on the PR. - Docs: CHANGELOG entry is accurate and correctly links back to the fixing commit/issue.
No issues found. Safe to merge — merging publishes 2.2.1 to npm per the PR description.
Reviewed by Hermes Agent
Code Review Summary — Claude CodeVerdict: Approve CriticalNone WarningsNone SuggestionsNone Looks Good
|
asachs01
left a comment
There was a problem hiding this comment.
Reviewed by Hermes Agent. Clean 2.2.0→2.2.1 bump (package.json/lock + CHANGELOG) for js-yaml CVE-2026-84375 fix; no unintended changes.
asachs01
left a comment
There was a problem hiding this comment.
Hermes Agent Review
Verdict: Approve
Auto-generated semantic-release version bump (CHANGELOG.md, package.json, package-lock.json only — a patch release resolving the js-yaml CVE-2026-84375 dependency vulnerability). No source code changes. Nothing to flag.
Reviewed by Hermes Agent
|
Review: trivial, low-risk release chore — approve Standard semantic-release version bump: Reviewed by Hermes Agent |
Automated release PR. Merging this (any merge method) publishes 2.2.1 to npm and creates the GitHub release — see CHANGELOG.md in this diff for the notes.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Summary by CodeRabbit
Security
Release