Skip to content

Conversation

@SoloJacobs
Copy link
Contributor

@SoloJacobs SoloJacobs commented Nov 24, 2025

Adds CHANGELOG entries.

For convenience, here the same list with the merge date and the author:

For now, is just fixed the capitalization and the markdown syntax in the titles. Feel free to suggest changes. Some entries may be replaced, depending on which requests we merge. I also have a complete list of the PRs I reviewed, and why they did not make into the changelog.

EDIT: Newly added entries below.

@siavashs
Copy link
Contributor

siavashs commented Dec 5, 2025

I would like #4745 to be included if merged then we can drop #4629 since with tracing we don't need the inhibition metrics anymore.
It might be annoying to users if we make a release with new metrics and then remove them.

Also few others I would like in 0.30 if possible:

@SoloJacobs
Copy link
Contributor Author

Yes, that is very reasonable :-)

Add CHANGELOG entries.

Signed-off-by: Solomon Jacobs <solomonjacobs@protonmail.com>
@SoloJacobs SoloJacobs force-pushed the release branch 2 times, most recently from b4a571a to bb9895d Compare December 7, 2025 11:28
Adds changes that have been merged after 2025-11-21 into main. The entry

Signed-off-by: Solomon Jacobs <solomonjacobs@protonmail.com>
@SoloJacobs SoloJacobs moved this from Backlog to In review in Alertmanager v0.30.0 Dec 7, 2025
@SoloJacobs SoloJacobs requested a review from SuperQ December 7, 2025 11:33
@SoloJacobs SoloJacobs marked this pull request as ready for review December 7, 2025 11:34
@SoloJacobs SoloJacobs changed the title (WIP) Prep release v0.30 Prep release v0.30 Dec 7, 2025
Copy link
Contributor

@siavashs siavashs left a comment

Choose a reason for hiding this comment

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

LGTM, thanks

Previously, the titles were left unchanged from the original PR. We now
make the following small adjustments:

* Prefixes such as `Feat` and `Fix` are omitted, if they are already
covered by `[FEATURE]` and `[BUGFIX]`.
* Words indicating the area of improvement are spelled lower case.
* Colon is followed by an upper case word.

Signed-off-by: Solomon Jacobs <solomonjacobs@protonmail.com>
@SoloJacobs
Copy link
Contributor Author

Thanks for the review, should be fixed now (including some additional changes, which are in line with the feedback).

@SuperQ SuperQ requested a review from ultrotter December 8, 2025 15:16
@SuperQ SuperQ changed the title Prep release v0.30 Release v0.30.0 Dec 9, 2025
@SuperQ SuperQ changed the title Release v0.30.0 Release v0.30.0-rc.0 Dec 9, 2025
@SuperQ
Copy link
Member

SuperQ commented Dec 9, 2025

Want to update the VERSION file and release date to today?

Signed-off-by: Solomon Jacobs <solomonjacobs@protonmail.com>
@SoloJacobs
Copy link
Contributor Author

Not sure if I got the part about the release date, but I gave it a shot. 🙃

Copy link
Member

@SuperQ SuperQ left a comment

Choose a reason for hiding this comment

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

The release date in the RELEASE.md is just a vague target for the release. We can cut things +- a few days. It's all up to the release manager.

* [ENHANCEMENT] ...
* [BUGFIX] ...

## 0.30.0-rc.0 / 2025-12-10
Copy link
Member

Choose a reason for hiding this comment

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

You set the VERSION to 0.30.0, do you intend to just cut a release or do you want to cut an RC first?

Suggested change
## 0.30.0-rc.0 / 2025-12-10
## 0.30.0 / 2025-12-10

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I would like to a rc first and have adjusted VERSION accordingly.

Signed-off-by: Solomon Jacobs <solomonjacobs@protonmail.com>
@SoloJacobs
Copy link
Contributor Author

I guess I'll try an expose my thought process a little bit here: I have some changes I'm holding off on, and I imagine others are feeling similarly. That is why I would create a new release branch as soon as possible.

Then we can wait a bit to see if there are any bug reports. It would also be nice to have a more complex test environment, but I currently don't have one. Maybe somebody will volunteer their environment.

@SoloJacobs SoloJacobs requested a review from SuperQ December 9, 2025 23:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In review

Development

Successfully merging this pull request may close these issues.

4 participants