chore(deps): update quay.io/prometheus/alertmanager docker tag to v0.31.1 #91
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/quay.io-prometheus-alertmanager-0.x
branch
from
2c0a36a to
5b038dc
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/quay.io-prometheus-alertmanager-0.x
branch
from
5b038dc to
439dc40
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/quay.io-prometheus-alertmanager-0.x
branch
from
439dc40 to
1292d75
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/quay.io-prometheus-alertmanager-0.x
branch
from
1292d75 to
a7e71fb
Compare
renovate
bot
force-pushed
the
renovate/quay.io-prometheus-alertmanager-0.x
branch
from
a7e71fb to
25cc351
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/quay.io-prometheus-alertmanager-0.x
branch
from
25cc351 to
84b33e8
Compare
renovate
bot
force-pushed
the
renovate/quay.io-prometheus-alertmanager-0.x
branch
from
84b33e8 to
dbbe51c
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/quay.io-prometheus-alertmanager-0.x
branch
from
dbbe51c to
388cbe9
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/quay.io-prometheus-alertmanager-0.x
branch
from
388cbe9 to
d4374d2
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/quay.io-prometheus-alertmanager-0.x
branch
from
d4374d2 to
9120b03
Compare
renovate
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.21.0→v0.31.1Release Notes
prometheus/alertmanager (quay.io/prometheus/alertmanager)
v0.31.1: 0.31.1 / 2026-02-11Compare Source
v0.31.0: 0.31.0 / 2026-02-02Compare Source
api_urlfield. #4908max-silence-size-bytes. #4805AlertmanagerClusterFailedToSendAlertsto exclude value 0. #4872slack_configattachments documentation links. #4802chat_id_fileconfiguration parameter. #4909group_byto override parent route. #4825spellcheck=falseattribute on silence filter input. #4811v0.30.1: 0.30.1 / 2026-01-12Compare Source
v0.30.0: 0.30.0 / 2025-12-15Compare Source
phantom_threadingto group email alerts into threads. #4623client_allowed_sans. #4706s/client/alerts_api/g' broken link in 0.29. #4718rocketchat_configdocs. #4767<mute_time_interval>was renamed. #4729v0.29.0: 0.29.0 / 2025-11-01Compare Source
FailedToSendAlerts. #4206otherin error messages for config. #4366v0.28.1: 0.28.1 / 2025-03-07Compare Source
--verbose. #4218rocketchat_configswritten asrocket_configsin docs. #4217--enable-featureflag. #4214slack_configsin docs. #4247v0.28.0: 0.28.0 / 2025-01-15Compare Source
GOMEMLIMIT, enable it via the feature flag--enable-feature=auto-gomemlimit. #3895GOMAXPROCS, enable it via the feature flag--enable-feature=auto-gomaxprocs. #3837--silences.max-silencesand--silences.max-silence-size-bytesto set them accordingly #3852 #3862 #3866 #3885 #3886 #3877/api/v2/alertsendpoint and the Alertmanager UI. #3793 #3797 #3792content,usernameandavatar_urlin the Discord integration.contentandusernamealso support templating. #4007GET api/v2/alertsandPOST api/v2/alertsAPI endpoint. #3961room_idin the WebEx integration can now be templated to allow for dynamic room IDs. #3801message_thread_idfor the Telegram integration. #3638sinceandhumanizeDurationfunctions to templates. This means users can now format time to more human-readable text. #3863dateandtzfunctions to templates. This means users can now format time in a specified format and also change the timezone to their specific locale. #3812ParseModeoption is now set explicitly in the Telegram integration. If we don't HTML tags had not been parsed by default. #4027url_filein the Webhook integration. #3800Route.ID()returns conflicting IDs. #3803amtool template renderwhen using the default values. #3725webhook_url_filefor both the Discord and Microsoft Teams integrations. #3728 #3745v0.27.0: 0.27.0 / 2024-02-28Compare Source
message. #3597api/v1/endpoints. These endpoints now log and return a deprecation message and respond with a status code of410. #2970--enable-feature=receiver-name-in-metricsto include the receiver name in the following metrics: #3045alertmanager_notifications_totalalertmanager_notifications_failed_totallalertmanager_notification_requests_totalalertmanager_notification_requests_failed_totalalertmanager_notification_latency_secondsalertmanager_inhibition_rulesthat counts the number of configured inhibition rules. #3681alertmanager_alerts_supressed_totalthat tracks muted alerts, it contains areasonlabel to indicate the source of the mute. #3565webhook_url_file. #3555webhook_url_file. #3555summary. #3616reason,contextCanceledandcontextDeadlineExceeded. #3631auth_password_fileare now trimmed of prefixed and suffixed whitespace. #3680scheme required for webhook urlwhen using amtool with--alertmanager.url. #3509AlertmanagerFailedToSendAlerts,AlertmanagerClusterFailedToSendAlerts, andAlertmanagerClusterFailedToSendAlertsto make sure they ignore thereasonlabel. #3599Removal of API v1
The Alertmanager
v1API has been deprecated since January 2019 with the release of Alertmanagerv0.16.0. With the release of version0.27.0it is now removed.A successful HTTP request to any of the
v1endpoints will log and return a deprecation message while responding with a status code of410.Please ensure you switch to the
v2equivalent endpoint in your integrations before upgrading.Alertmanager support for all UTF-8 characters in matchers and label names
Starting with Alertmanager
v0.27.0, we have a new parser for matchers that has a number of backwards incompatible changes. While most matchers will be forward-compatible, some will not. Alertmanager is operating a transition period where it supports both UTF-8 and classic matchers, so it's entirely safe to upgrade without any additional configuration. With that said, we recommend the following:If this is a new Alertmanager installation, we recommend enabling UTF-8 strict mode before creating an Alertmanager configuration file. You can enable strict mode with
alertmanager --config.file=config.yml --enable-feature="utf8-strict-mode".If this is an existing Alertmanager installation, we recommend running the Alertmanager in the default mode called fallback mode before enabling UTF-8 strict mode. In this mode, Alertmanager will log a warning if you need to make any changes to your configuration file before UTF-8 strict mode can be enabled. Alertmanager will make UTF-8 strict mode the default in the next two versions, so it's important to transition as soon as possible.
Irrespective of whether an Alertmanager installation is a new or existing installation, you can also use
amtoolto validate that an Alertmanager configuration file is compatible with UTF-8 strict mode before enabling it in Alertmanager server by runningamtool check-config config.ymland inspecting the log messages.Should you encounter any problems, you can run the Alertmanager with just the classic parser enabled by running
alertmanager --config.file=config.yml --enable-feature="classic-mode". If so, please submit a bug report via GitHub issues.v0.26.0: 0.26.0 / 2023-08-23Compare Source
api_urlis now optional. #2981ParseModedefault is nowHTMLinstead ofMarkdownV2. #2981urlis now marked as a secret. It will no longer show up in the logs as clear-text. #3228reasonforalertmanager_notifications_failed_totalmetric to indicate the type of error of the alert delivery. #3094 #3307--cluster.label, to help to block any traffic that is not meant for the cluster. #3354bot_token_filefor loading this secret from a file. #3226url_filefor loading this secret from a file. #3223url_file. #3363deviceandsound(sound was previously supported but undocumented). #3318user_key_fileandtoken_filefor loading this secret from a file. #3200CORSandCache-ControlHTTP headers to all version 2 API routes. #3195{{ .Annotations }}and{{ .Labels }}. #3256trimSpacewhich removes leading and trailing white spaces. #3223amtool silence querynow supports the--idflag to query an individual silence. #3241alertmanager_nflog_maintenance_totalandalertmanager_nflog_maintenance_errors_totalto monitor maintenance of the notification log. #3286alertmanager_silences_maintenance_totalandalertmanager_silences_maintenance_errors_totalto monitor maintenance of silences. #3285receiversandinhibit_ruleswould cause the alertmanager to crash. #3209titlefunction. It is now race-safe. #3278api/v2/receiversAPI endpoint. #3338404instead of500. #3352tls_client_configis empty. #3443v0.25.1: 0.25.1 / 2023-08-23Compare Source
v0.25.0: 0.25.0 / 2022-12-22Compare Source
parse_modevalue fromMarkdownV2toHTMLfor Telegram. #2981api_urlfield optional for Telegram. #2981proxy_urlsupport for OAuth2 in HTTP client configuration. #3010--web.systemd-socketflag to systemd socket activation listeners instead of port listeners (Linux only). #3140enable_http2support in HTTP client configuration. #3010min_versionsupport to select the minimum TLS version in HTTP client configuration. #3010max_versionsupport to select the maximum TLS version in HTTP client configuration. #3168--data.maintenance-intervalflag to define the interval between the garbage collection and snapshotting to disk of the silences and the notification logs. #2849/-/healtyand/-/readyendpoints. #3039…ellipsis character instead of the 3-dots string.... #3072sourcefield to the PagerDuty configuration. #3106api_keyandapi_key_fileare defined at the same time. #2910alertmanager_alertsmetric to avoid counting resolved alerts as active. Also added a newalertmanager_marked_alertsmetric that retain the old behavior. #2943api_urlis empty for OpsGenie. #2910v0.24.0: 0.24.0 / 2022-03-24Compare Source
/api/v2prefix to all endpoints in the OpenAPI specification and generated client code. #2696github.com/prometheus/alertmanager/clientGo package. #2763--cluster.tls-configexperimental flag to secure cluster traffic via mutual TLS. #2237time_intervalsrather thanmute_time_intervals(the latter is deprecated but it will be supported until v1.0). #2779update_alertsfield to the OpsGenie configuration to update message and description when sending alerts. #2519--cluster.allow-insecure-public-advertise-address-discoveryfeature flag to enable discovery and use of public IP addresses for clustering. #2719entityandactionsfields to the OpsGenie configuration. #2753opsgenie_api_key_filefield to the global configuration. #2728teamsresponders to the OpsGenie configuration. #2685createdByauthor. #2718--http.config.fileflag to configure HTTP settings. #2764mute_time_intervalsin JSON marshaling. #2765email.default.html) to match with the canonical source. #2798v0.23.0: 0.23.0 / 2021-08-25Compare Source
v0.22.2: 0.22.2 / 2021-06-01Compare Source
v0.22.1: 0.22.1 / 2021-05-27Compare Source
This release addresses a regression in the API v1 that was introduced in 0.22.0.
Matchers in silences created with the API v1 could be considered negative
matchers. This affects users using amtool prior to v0.17.0.
v0.22.0: 0.22.0 / 2021-05-21Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.