Strip the bot's [WRONG BRANCH] prefix from release summaries and full changelogs #3895

Client or integration

Other (GitHub release notes generated by scripts/release-notes.ts)

Area

Installation or packaging

Summary

The v2.45.0 release includes the PR-enforcement bot's [WRONG BRANCH] title prefix in both a category bullet and the full changelog.

Two rendering paths preserve it at dev commit 76436a3ee221d577cc94d6c10544c03bb1f9d9db:

• cleanPrTitle recognizes conventional prefixes only at the start of the title. The bot prefix prevents both cleanup and scope extraction.
• Full changelog rendering uses pr.title.trim() directly. Fixing only cleanPrTitle therefore leaves the changelog occurrence intact.

Expected: remove the known leading bot prefix from both rendered paths. Category bullets should retain their existing conventional-prefix cleanup and sentence casing; the full changelog should retain the conventional title, PR number, and author.

The bot's title marker is defined in enforce-pr-target.yml. This report does not propose relaxing that enforcement workflow.

Reproduction

1. Open the v2.45.0 release linked above and search for WRONG BRANCH. It appears in both sections.
2. From the reviewed checkout, evaluate these pure helpers with Bun:

import { cleanPrTitle, renderReleaseNotes } from "./scripts/release-notes";

const title = "[WRONG BRANCH] chore(release): promote validated 2.45.0 to main";
console.log(cleanPrTitle(title, 3813));
console.log(renderReleaseNotes({
  npmMetadata: "",
  deltaPrNotes: [
    "## What's Changed",
    "### Chores",
    `* ${title} by @lidge-jun in https://github.com/lidge-jun/opencodex/pull/3813`,
  ].join("\n"),
}));

Current helper result:

{"scope":null,"text":"[WRONG BRANCH] chore(release): promote validated 2.45.0 to main"}

Expected helper result:

{"scope":"release","text":"Promote validated 2.45.0 to main"}

Expected category bullet:

- Promote validated 2.45.0 to main (#3813)

Expected full changelog entry:

- #3813 chore(release): promote validated 2.45.0 to main @lidge-jun

Add a regression that exercises the complete renderer and asserts both output paths. Also preserve ordinary unprefixed titles, meaningful bracketed text other than the known bot marker, PR references, and author attribution. A helper-only assertion is insufficient.

Version

Source reproduced at dev commit 76436a3; also verified in the published v2.45.0 release.

Operating system

Locally reproduced on Windows with Bun 1.4.0. The affected code is a pure release-note renderer.

Provider and model

The reproduction does not invoke a provider or model.

Logs or error output

Actual complete-renderer output:

## Chores

- [WRONG BRANCH] chore(release): promote validated 2.45.0 to main (#3813)

## Changelog

- #3813 [WRONG BRANCH] chore(release): promote validated 2.45.0 to main @lidge-jun

Screenshots and supporting files

The published release and pinned source links above provide the artifacts. All 71 existing tests in tests/ci-workflows/release-notes.test.ts passed during review; the prefixed-title case was reproduced separately.

No conclusion about why v2.46.0 rendered differently is needed for this reproduction. Workflow timing has not been established.

Redacted configuration

{}

The minimal reproduction uses the literal title and note body above; no user configuration or credentials are involved.

Checks

• I searched existing issues and documentation.
• I removed secrets, tokens, account details, request credentials, and personal data.