Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

ci(release-drafter): escape @ and # in release-note PR titles#1475

Merged
dimitri-yatsenko merged 1 commit into
masterfrom
fix/release-drafter-escape-mentions
Jul 2, 2026
Merged

ci(release-drafter): escape @ and # in release-note PR titles#1475
dimitri-yatsenko merged 1 commit into
masterfrom
fix/release-drafter-escape-mentions

Conversation

@dimitri-yatsenko

Copy link
Copy Markdown
Member

Problem

On the drafted v2.3.0 release notes, @schema from PR #1467's title ("refresh ~lineage on every @schema decoration") rendered as a live GitHub user mention, so "Schema" showed up as a contributor/co-author on the release. Same mechanism auto-links the #1425/#1429/… issue refs inside conventional-commit titles.

Cause

release_drafter.yaml's change-title-escapes was '\<*_&' — it omits @ and #, so mention/issue text inside PR titles renders live. The config comment already notes: "You can add # and @ to disable mentions."

Fix

change-title-escapes: '\<*_&@#'. Title text stays literal; the template's real @$AUTHOR credit and the (#$NUMBER) PR link are unaffected (those come from the template, not the escaped title).

Takes effect the next time the draft workflow runs. The current v2.3.0 draft body was hand-corrected separately for this release.

PR titles that mention a decorator (e.g. `@schema`) or an issue (e.g.
`feat(#1425):`) were rendering as live GitHub mentions/links in the drafted
release notes — the `@schema` in #1467's title showed up as a spurious
"Schema" contributor on the v2.3.0 draft. Add @ and # to change-title-escapes
(the config comment already documents this) so title text stays literal while
the template's real $AUTHOR credit and (#PR) link are unaffected.
@dimitri-yatsenko dimitri-yatsenko merged commit b50840c into master Jul 2, 2026
3 checks passed
@dimitri-yatsenko dimitri-yatsenko deleted the fix/release-drafter-escape-mentions branch July 2, 2026 20:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants