feat: filters items out of the release process that aren't for backports#553
feat: filters items out of the release process that aren't for backports#553owlstronaut merged 1 commit intomainfrom
Conversation
| return false | ||
| } | ||
|
|
||
| if (isBackport && item.includes('<!-- NOT FOR BACKPORT -->')) { |
There was a problem hiding this comment.
This is the only part that gives me pause. There is no way I'm gonna remember this comment in the source markdown is how the filter works.
There was a problem hiding this comment.
Fair point — I liked the HTML comment approach since it keeps the checklist clean for the common (non-backport) case, but I agree discoverability matters here too. Happy to switch it to match the > NOT FOR PRERELEASE pattern if you think that's the way to go.
There was a problem hiding this comment.
Yeah sorry this is one of those "complaints without a solution". In the absence of a better idea we can ship this. I just know I get so lost every time I have to update that markdown file in the first place. Maybe discoverability of that should be something we can work on.
🤖 I have created a release *beep* *boop* --- ## [4.30.0](v4.29.0...v4.30.0) (2026-03-19) ### Features * [`6bc2bc0`](6bc2bc0) [#553](#553) filters items out of the release process that aren't for backports (#553) (@owlstronaut) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2 participants
This pull request adds automated backport detection and filtering logic to the release process, ensuring that steps not relevant for backports are excluded from the checklist. It also introduces new tests and fixtures to verify this functionality.