chore: change webhook url for releases#2615
Merged
hugohaggmark merged 1 commit intomainfrom May 6, 2026
Merged
Conversation
Contributor
|
Hello! 👋 This repository uses Auto for releasing packages using PR labels. ✨ This PR can be merged. It will not be considered when calculating future versions of the npm packages and will not appear in the changelogs. |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Slack webhook secret reference used by the release job in the main CI workflow so that release notifications are sent to the intended Slack channel.
Changes:
- Switches the Vault secret key used to populate
SLACK_WEBHOOK_URLfor the release workflow (slack_webhook_url_fpinstead ofslack_webhook_url).
sunker
approved these changes
May 6, 2026
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
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.
What is this feature?
Updates the Slack webhook URL secret reference in the release workflow.
Why do we need this feature?
So release notifications get posted to the correct Slack channel.
Who is this feature for?
Grafana maintainers
Which issue(s) does this PR fix?:
Fixes #
Special notes for your reviewer:
Please check that: