Repository navigation
chore(main): release 2.2.0-rc.1 - #2071
github-actions[bot] wants to merge 1 commit into
Conversation
8cf66af to
051d53b
Compare
hckrman101
left a comment
There was a problem hiding this comment.
DO NOT MERGE UNTIL 2026-11-11 morning~
b44eaca to
5d10233
Compare
d7122a5 to
3149824
Compare
43eb513 to
284298e
Compare
hckrman101
left a comment
There was a problem hiding this comment.
Re-review at f2aef72 (the head moved on from the 284298e this was queued at). My earlier note was the hold until the morning of 2026-11-11; v2.1.0 was published today, so that hold is over. Cutting the release is NotRexed's call, so this is a comment, not an approval.
Checked:
- Version: 2.1.0 -> 2.2.0-rc.1 is right for this range. There are 28
featcommits and no!orBREAKING CHANGE, and docs/versioning.md says afeatafter a release proposes the next minor atrc.1. The manifest is a one-line change and matches the compare linkv2.1.0...v2.2.0-rc.1. - Changelog: all 159 commit links point at commits in
v2.1.0..main; nothing already shipped in 2.1.0 is repeated (the stalelast-release-shain the config did not leak anything). Sections and counts match the commit types (28 feat, 87 fix, 15 perf, 9 build, 5 ci, 5 docs, 13 test, 2 chore). The non-conventional commits (readme and Discord link edits, the #1947 fix) are left out, as expected.
Open, none blocking:
- The PR was generated from 9b7fa52, and main has moved since. Four newer commits are not in this changelog yet: #2119 (feat, the Aspect ratio row), #2513, #2524 (fixes) and #2518 (build). If the PR is merged as it is, the tag lands on a main that contains them but the notes omit them. Let the bot refresh it first (or merge only after it has), then re-check.
- Nit: docs/versioning.md says the release PR also writes
.release-please-version, but the PR touches only the manifest and CHANGELOG, and the file does not exist on main. Harmless for this release, but either the doc or the config is off. - No checks are reported on the release branch (normal for a PR pushed by the Actions token), so the usual CI has not run on this exact commit. It only changes the manifest and the changelog.
hckrman101
left a comment
There was a problem hiding this comment.
Re-checked at 7ae362e. The four entries I flagged earlier (#2119, #2513, #2524, #2518) are now in the notes, and the changelog has no duplicate commits. Every feat/fix/perf commit on main up to this push is covered. The version (2.2.0-rc.1) and the manifest (.: 2.2.0-rc.1) agree, and those are the only two files touched.
One thing to know: #2325 and #2407 merged to main after this push, so they are not in the notes yet. The bot should add them on its next refresh, so check for them before cutting the release.
Whether and when to release stays with @NotRexed.
🤖 I have created a release beep boop
2.2.0-rc.1 (2026-11-12)
Features
Bug Fixes
Performance Improvements
Build System
Continuous Integration
Documentation
Tests
Miscellaneous Chores
This PR was generated with Release Please. See documentation.