chore(main): release 2.32.0 - #1925
Merged
Merged
Conversation
Signed-off-by: misakanet-bot <bot@misakanet.dev>
Contributor
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
misakanet-web | d3d155e | Commit Preview URL Branch Preview URL |
Sep 20 2026, 09:57 AM |
Contributor
PR Genius Analysis
Checklist
Anti-Patterns Detected
Suggestions
|
Owner
Author
🧾 Audit Report — PR #1925 (d3d155e)📊 Quality Score🔏 DCO Audit✅ All commits signed-off. 📏 PR Size
🔐 Secret Scan✅ No hardcoded secrets detected. 📦 Dependency Audit✅ No known vulnerabilities in changed dependency ecosystem(s). 🧪 Test Suite✅ PASS — 54% coverage 📋 Lesson Schema✅ All lessons valid. ⚖️ Verdict✅ All gates passed. Ready for merge. Scope: |
Contributor
🎉 Merged — Thank you!Your contribution has been merged into main. PR: #1925 — chore(main): release 2.32.0 What's next:
Welcome to the MisakaNet contributor community! 🧠 |
Contributor
|
✅ Merged! Thanks again, @Ikalus1988. chore(main): release 2.32.0 (+125 lines, 12 files) Quick question — did any MisakaNet lesson help you this time? No need to reply if nothing comes to mind. ⚡ |
3 tasks
zsxh1990
pushed a commit
to zsxh1990/MisakaNet
that referenced
this pull request
Sep 21, 2026
…d before it ships Two things surfaced from the same event: the auto-merge gate merged the **2.32.0 release PR at 09:59 while the maintainer was still reviewing its changelog**, and that changelog turned out to hold **30 duplicated entries** — 91 bullet lines covering 61 changes. It shipped as `v2.32.0`, and `release-please` immediately prepared `2.32.1` (also auto-merged), which had the same defect on its single entry. **Why the entries doubled.** release-please builds notes from conventional commits, and a merge commit whose message also carries the conventional subject is counted *next to* the branch commit it merged. This repository hit that before and fixed it in one place — `pr-checks.yml` dropped `gh pr merge --subject` "Auto-merge #N: …" for exactly this reason — but the shape came back from two directions: merge commits created through the API with `commit_title` set to the PR title (mine, for Ikalus1988#1876/Ikalus1988#1799/Ikalus1988#1905/Ikalus1988#1907 and earlier), and merge commits whose *body* GitHub fills with the PR title (Ikalus1988#1926, merged by the gate with the default subject). Only `CHANGELOG.md` is affected: the GitHub Release body is generated by GitHub's own notes and was clean. **The three parts, in the order they matter:** 1. **Release PRs are excluded from auto-merge.** They are the one artifact a person should read before it ships: a version bump plus the changelog that becomes the release notes, prepared by a bot, read by nobody. Detected by the `autorelease:` label release-please maintains, with the `release-please--` branch name as a fallback for the window before the label lands. 2. **`tests/test_changelog_shape.py`** fails when the newest release section lists the same change twice. It is a pre-release gate by design: the release PR is what carries a new section, so it goes red *there*, where a human can dedupe before shipping — which is what Ikalus1988#1925 needed. 3. **The shipped changelogs are deduped**: `2.32.0` 91 → 61 entries, `2.32.1` 2 → 1. History is otherwise left alone (`2.31.0` still carries 4 duplicated pairs from the earlier era; rewriting released sections is not worth it). Each rule has a guard-the-guard test that mutates a scratch copy, so neither can silently become decoration. Signed-off-by: Ikalus1988 <136884451+Ikalus1988@users.noreply.github.com>
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
1 participant
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.
🤖 I have created a release beep boop
2.32.0 (2026-09-20)
Features
Bug Fixes
Documentation
Tests
CI/CD
This PR was generated with Release Please. See documentation.