Skip to content

ci: Allow release note enrichment when "closes" is present [backport]#5400

Merged
jharvey10 merged 1 commit intorelease/v1.13from
backport/pr-5398-to-v1.13
Jan 29, 2026
Merged

ci: Allow release note enrichment when "closes" is present [backport]#5400
jharvey10 merged 1 commit intorelease/v1.13from
backport/pr-5398-to-v1.13

Conversation

@grafana-alloybot
Copy link
Contributor

Backport of #5398

This PR backports #5398 to release/v1.13.

Original PR Author

@jharvey10

Description

An interesting thing I discovered with release please is that if a commit has a reference to a closed issue, this will be called out in the changelog 🎉

For example:

* Invalid handling of id in foreach when using discovery components (#5322) (61fe184), closes #5297

The only problem is this breaks the way I wrote the regex for the release not enrichment script. This PR fixes that.


This backport was created automatically.

An interesting thing I discovered with release please is that if a
commit has a reference to a closed issue, this will be called out in the
changelog 🎉

For example:

```
* Invalid handling of id in foreach when using discovery components (\#5322) (61fe184), closes \#5297
```

The only problem is this breaks the way I wrote the regex for the
release not enrichment script. This PR fixes that.

(cherry picked from commit 8cfe2f1)
@grafana-alloybot grafana-alloybot bot requested a review from a team as a code owner January 29, 2026 21:33
@jharvey10 jharvey10 enabled auto-merge (squash) January 29, 2026 21:34
@jharvey10 jharvey10 merged commit 6d726bf into release/v1.13 Jan 29, 2026
43 checks passed
@jharvey10 jharvey10 deleted the backport/pr-5398-to-v1.13 branch January 29, 2026 21:51
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 13, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant