Repository navigation
chore(main): release 2.2.1 - #49
github-actions[bot] wants to merge 1 commit into
Conversation
34e0747 to
0b1f545
Compare
0b1f545 to
65164c0
Compare
choskeli
left a comment
There was a problem hiding this comment.
Atlas Merge Warden — prod review-gate
🟠 Escalated — not releasable yet for base branch main (protected prod branch).
| Check | Status |
|---|---|
| Structured review | ✅ approve |
| Confidence | 95 (input only) |
| Release readiness | 🔴 not ready |
| Head reviewed | 65164c0afe2b7f2151c50626ea4ab250a045363a |
| Policy version | 40ed1b85e9bf8e0c |
Required checks at head 65164c0afe2b7f2151c50626ea4ab250a045363a:
| Check | Observation |
|---|---|
| (no required checks resolved) | (unconfigured) |
MW does not merge in review-gate mode. After approval, the agent that opened this PR merges it.
Reasons:
- no required check policy configured for prod branch 'main'
Summary: Automated release-please PR bumping the package version from 2.2.0 to 2.2.1. All four changed files (.release-please-manifest.json, package.json, both package.json entries in package-lock.json) are bumped consistently, and CHANGELOG.md follows the standard generated format with correctly formed compare links and commit hashes. No executable code, dependency-range, secret, or data-loss changes are present; the merge-queue fix/revert pair in the changelog is expected release-please output. Safe to
Findings:
- [informational] Changelog contains a fix/revert pair; net effect is nil
🤖 I have created a release beep boop
2.2.1 (2026-10-28)
Fixes
Reverts
This PR was generated with Release Please. See documentation.