Skip to content

feat(cicd): add auto next release parser#1462

Open
aeppling wants to merge 1 commit intodevelopfrom
cicd-auto-next-release
Open

feat(cicd): add auto next release parser#1462
aeppling wants to merge 1 commit intodevelopfrom
cicd-auto-next-release

Conversation

@aeppling
Copy link
Copy Markdown
Contributor

@aeppling aeppling commented Apr 22, 2026

Create Next Release PR and set up the description with fix / feat PRs and issues to be closed

● 18/18 passed. All functional scenarios verified:

┌──────┬────────────────────────────────────────────────────────────────┐
│ Test │ What it proves │
├──────┼────────────────────────────────────────────────────────────────┤
│ 1-5 │ Entry line format is exact match for feat/fix/other │
├──────┼────────────────────────────────────────────────────────────────┤
│ 2,4 │ Single issue ref parsed from Closes #N and full GitHub URL │
├──────┼────────────────────────────────────────────────────────────────┤
│ 3 │ Multiple issue refs both extracted │
├──────┼────────────────────────────────────────────────────────────────┤
│ 6-8 │ Insertion into each section of empty template │
├──────┼────────────────────────────────────────────────────────────────┤
│ 9 │ Second feat inserts at top (newest first) │
├──────┼────────────────────────────────────────────────────────────────┤
│ 10 │ Insertion into populated body with entries in all 3 sections │
├──────┼────────────────────────────────────────────────────────────────┤
│ 11 │ Case-insensitive keywords (CLOSES, fixes, Resolves) │
├──────┼────────────────────────────────────────────────────────────────┤
│ 12 │ Body with no issue refs produces clean entry (no trailing —) │
├──────┼────────────────────────────────────────────────────────────────┤
│ 13 │ Duplicate refs deduplicated to one │
├──────┼────────────────────────────────────────────────────────────────┤
│ 14 │ Classification is case-insensitive (Feat, FEAT, FIX) │
└──────┴────────────────────────────────────────────────────────────────┘

Create Next Release PR and set up the description with fix / feat PRs and issues to be closed
@aeppling aeppling self-assigned this Apr 22, 2026
Copy link
Copy Markdown
Collaborator

@KuSh KuSh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Otherwise LGTM!

ISSUE_REFS=""
if [ -n "$PR_BODY" ]; then
ISSUE_REFS=$(echo "$PR_BODY" \
| grep -oiE '(closes|fixes|resolves)\s+#[0-9]+|https://github\.com/[^/]+/[^/]+/issues/[0-9]+' \
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| grep -oiE '(closes|fixes|resolves)\s+#[0-9]+|https://github\.com/[^/]+/[^/]+/issues/[0-9]+' \
| grep -oiE '(closes|fixes|resolves):?\s+#[0-9]+|https://github\.com/[^/]+/[^/]+/issues/[0-9]+' \

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also perhaps filter on our own repo to avoid catching references to issues on other ones

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