Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

grafana 10.4.0 #165251

Closed
wants to merge 1 commit into from
Closed

grafana 10.4.0 #165251

wants to merge 1 commit into from

Conversation

BrewTestBot
Copy link
Member

Created by brew bump


Created with brew bump-formula-pr.

release notes
[Download page](https://grafana.com/grafana/download/10.4.0)
[What's new highlights](https://grafana.com/docs/grafana/latest/whatsnew/)

Features and enhancements

Bug fixes

Breaking changes

We're adding a between the response of the ID token HD parameter and the list of allowed domains. This feature can be disabled through the configuration toggle validate_hd . Anyone using the legacy Google OAuth configuration should disable this validation if the ID Token response doesn't have the HD parameter. Issue #83726

If you use an automated provisioning (eg, Terraform) for custom roles, and have provisioned a role that includes permission with action alert.instances:read and some scope, you will need to update the permission in your provisioning files by removing the scope. Issue #82202

The following breaking change occurs only when feature flag nestedFolders is enabled.
If the folder title contains the symbol / (forward-slash) the notifications created from the rules that are placed in that folder will contain an escape sequence for that symbol in the label grafana_folder.
For example, the folder title is Grafana / Folder. Currently the label grafana_folder will contain the title as it is. If PR is merged - the label value will be Grafana \/ Folder.
This can break notifications if notification policies have matches that match that label and folder. Issue #81214

PanelContext.onSplitOpen is removed. In the context of Explore, plugins should use field.getLinks to get a list of data link models. Issue #80087

The unstable alert rule API has been changed and now expects a folder UID instead of the folder title as namespace path parameter.
I addition to this, the responses that used to return the folder title now return <folder parent UID>/<folder title> to uniquely identify them.
Any consumers of the specific API should be appropriately adapted. Issue #74600

Plugin development fixes & changes

@github-actions github-actions bot added go Go use is a significant feature of the PR or issue nodejs Node or npm use is a significant feature of the PR or issue bump-formula-pr PR was created using `brew bump-formula-pr` labels Mar 6, 2024
@chenrui333
Copy link
Member

➤ YN0009: @esfx/equatable@npm:1.0.2 couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-e6a00222/build.log)

grafana: update build

Signed-off-by: Rui Chen <rui@chenrui.dev>
Copy link
Contributor

github-actions bot commented Mar 8, 2024

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. To keep this pull request open, add a help wanted or in progress label.

@github-actions github-actions bot added the stale No recent activity label Mar 8, 2024
@github-actions github-actions bot closed this Mar 10, 2024
@chenrui333 chenrui333 deleted the bump-grafana-10.4.0 branch March 14, 2024 00:52
@github-actions github-actions bot added the outdated PR was locked due to age label Apr 13, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bump-formula-pr PR was created using `brew bump-formula-pr` go Go use is a significant feature of the PR or issue nodejs Node or npm use is a significant feature of the PR or issue outdated PR was locked due to age stale No recent activity
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants