Skip to content

Release v0.32.0#5155

Merged
ultrotter merged 1 commit intoprometheus:mainfrom
SoloJacobs:release-coordination
Apr 7, 2026
Merged

Release v0.32.0#5155
ultrotter merged 1 commit intoprometheus:mainfrom
SoloJacobs:release-coordination

Conversation

@SoloJacobs
Copy link
Copy Markdown
Contributor

@SoloJacobs SoloJacobs commented Apr 6, 2026

Summary by CodeRabbit

Release Notes: Version 0.32.0

  • New Features

    • Enhanced silence management with annotations and logging capabilities
    • Improved template and webhook payload templating
    • Support for multiple matcher set silences
  • Performance Improvements

    • Static asset caching optimization
    • Memory allocation enhancements
  • Deprecations

    • --enable-feature=auto-gomaxprocs flag
  • Bug Fixes & Enhancements

    • Configuration, UI, notifier, and telemetry fixes

* [CHANGE] `go get github.com/prometheus/alertmanager/ui` will now fail as compiled UI assets are no longer checked into the repository. Downstream builds that rely on these assets being present in the source tree must now build the UI from source. prometheus#5113
* [CHANGE] The '--enable-feature=auto-gomaxprocs' option is deprecated and will be removed in v0.33. This flag currently has no effect and can be safely removed from any startup scripts. prometheus#5090
* [CHANGE] Update internal function signatures across multiple packages. This affects any project that integrates `Alertmanager` code.
* [ENHANCEMENT] Add static asset caching. prometheus#5113
* [ENHANCEMENT] Reduce memory allocations through pre-sizing collections and batch allocation. prometheus#5020
* [ENHANCEMENT] Replace help with documentation in navigation bar. prometheus#4943
* [ENHANCEMENT] docs(ha): Update high availability documentation. prometheus#5136
* [ENHANCEMENT] docs: Add `auth_secret_file` for smtp in document. prometheus#5036
* [ENHANCEMENT] docs: Add description for global `telegram_bot_token`. prometheus#5114
* [ENHANCEMENT] docs: Add note about notifier timeouts. prometheus#5077
* [ENHANCEMENT] docs: Fix `force_implicit_tls` config field name. prometheus#5030
* [ENHANCEMENT] docs: Link community supported integrations. prometheus#4978
* [ENHANCEMENT] docs: Remove duplicate header. prometheus#5034
* [ENHANCEMENT] docs: Update mutual tls reference in high availability documentation. prometheus#5120
* [ENHANCEMENT] tracing: Use noop spans when tracing disabled. prometheus#5118
* [FEATURE] Add silence annotations. prometheus#4965
* [FEATURE] Add silence logging option. prometheus#4163
* [FEATURE] Add support for multiple matcher set silences. prometheus#4957
* [FEATURE] Add the reason for notifying in dedup stage. prometheus#4971
* [FEATURE] mattermost: Flatten attachments into top-level config. prometheus#5009
* [FEATURE] mattermost: Support global webhook url. prometheus#4998
* [FEATURE] slack: Add default color from template. prometheus#5014
* [FEATURE] slack: Allow receiver to edit existing messages. prometheus#5007
* [FEATURE] template: Add dict, map and append functions. prometheus#5093
* [FEATURE] webhook: Add full payload templating support for notifier. prometheus#5011
* [BUGFIX] config: Check for empty cluster tls client config. prometheus#5126
* [BUGFIX] config: Don't crash upon reading empty config for notifier. prometheus#4979
* [BUGFIX] config: Fix ipv6 address handling in hostport.string(). prometheus#5040
* [BUGFIX] mattermost: Omit empty text field in notifications. prometheus#4985
* [BUGFIX] telegram: Send fallback message when notification exceeds character limit. prometheus#5074
* [BUGFIX] ui: Fix escaping for matcher values with quotes. prometheus#4862
* [BUGFIX] ui: Handle special chars in silence regex-matchers. prometheus#4942
* [BUGFIX] ui: Support utf-8 label names in matchers. prometheus#5089

Signed-off-by: Solomon Jacobs <solomonjacobs@protonmail.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 6, 2026

📝 Walkthrough

Walkthrough

Version 0.32.0 release preparation. The VERSION file was incremented from 0.31.1 to 0.32.0, and the CHANGELOG.md was updated with a new populated release section containing categorized entries for features, enhancements, changes, and bugfixes.

Changes

Cohort / File(s) Summary
Release Versioning
VERSION
Version number incremented from 0.31.1 to 0.32.0.
Release Changelog
CHANGELOG.md
Replaced placeholder "main / (unreleased)" section with fully populated v0.32.0 (2026-04-10) release notes. Added categorized entries including feature deprecations, behavioral changes, new silence-related capabilities, template/webhook enhancements, and various fixes across config, UI, notifiers, and telemetry.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description lists merged PRs/issues but lacks required sections from the template: no 'Pull Request Checklist' items are checked, no issue links are properly formatted with 'Fixes', and the 'Which user-facing changes' section is empty. Complete the PR checklist by checking applicable boxes, properly link issues using 'Fixes #' format, and fill the release-notes section with formatted changelog entries similar to those in the commit messages.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Release v0.32.0' clearly and directly summarizes the main purpose of the PR, which is to release version 0.32.0 as evidenced by VERSION and CHANGELOG.md file changes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@SoloJacobs
Copy link
Copy Markdown
Contributor Author

@siavashs I ended up not including any of Change descriptions, which where generic function signature changes. We have many changes in this release, which did not document this as diligently as you did. So, rather than having an incomplete list, I decided to put a generic warning at the top of our release. Please have a look if that works for you.

@SoloJacobs SoloJacobs marked this pull request as ready for review April 6, 2026 13:32
@SoloJacobs SoloJacobs requested a review from a team as a code owner April 6, 2026 13:32
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
CHANGELOG.md (1)

11-11: Add traceability for the integrator-impacting change entry.

Line 11 describes a broad breaking-impact area but lacks issue/PR references unlike neighboring items. Please add the relevant PR numbers (or an umbrella tracking issue) for auditability.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` at line 11, Update the CHANGELOG entry that reads "Update
internal function signatures across multiple packages... Alertmanager" to
include specific traceability (e.g., add the relevant PR numbers or an umbrella
issue reference) so integrators can audit the change; specifically edit the
bullet mentioning "Alertmanager" and "internal function signatures" to append
the PR/issue identifiers (e.g., "See PR `#1234`, `#1235`" or "tracking issue `#5678`")
and, if other entries use a consistent format, match that format for links and
spacing.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CHANGELOG.md`:
- Line 20: Update the CHANGELOG entry "* [ENHANCEMENT] docs: Link community
supported integrations. `#4978`" to hyphenate the compound adjective by changing
"community supported" to "community-supported" so the line reads "*
[ENHANCEMENT] docs: Link community-supported integrations. `#4978`".

---

Nitpick comments:
In `@CHANGELOG.md`:
- Line 11: Update the CHANGELOG entry that reads "Update internal function
signatures across multiple packages... Alertmanager" to include specific
traceability (e.g., add the relevant PR numbers or an umbrella issue reference)
so integrators can audit the change; specifically edit the bullet mentioning
"Alertmanager" and "internal function signatures" to append the PR/issue
identifiers (e.g., "See PR `#1234`, `#1235`" or "tracking issue `#5678`") and, if
other entries use a consistent format, match that format for links and spacing.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: f1fcc2ce-c04a-4f8c-89cc-2a3c79bd572f

📥 Commits

Reviewing files that changed from the base of the PR and between 97c8a53 and 37e53df.

📒 Files selected for processing (2)
  • CHANGELOG.md
  • VERSION

Comment thread CHANGELOG.md
* [ENHANCEMENT] docs: Add description for global `telegram_bot_token`. #5114
* [ENHANCEMENT] docs: Add note about notifier timeouts. #5077
* [ENHANCEMENT] docs: Fix `force_implicit_tls` config field name. #5030
* [ENHANCEMENT] docs: Link community supported integrations. #4978
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Hyphenate “community-supported” in docs entry.

Line 20 should use the compound adjective form for readability.

✍️ Proposed wording tweak
-* [ENHANCEMENT] docs: Link community supported integrations. `#4978`
+* [ENHANCEMENT] docs: Link community-supported integrations. `#4978`
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
* [ENHANCEMENT] docs: Link community supported integrations. #4978
* [ENHANCEMENT] docs: Link community-supported integrations. `#4978`
🧰 Tools
🪛 LanguageTool

[grammar] ~20-~20: Use a hyphen to join words.
Context: ...030 * [ENHANCEMENT] docs: Link community supported integrations. #4978 * [ENHANCE...

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` at line 20, Update the CHANGELOG entry "* [ENHANCEMENT] docs:
Link community supported integrations. `#4978`" to hyphenate the compound
adjective by changing "community supported" to "community-supported" so the line
reads "* [ENHANCEMENT] docs: Link community-supported integrations. `#4978`".

@ultrotter ultrotter merged commit 5637381 into prometheus:main Apr 7, 2026
7 checks passed
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.

3 participants