Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 15, 2025

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
grafana (source) minor 10.1.0 -> 10.4.0

Release Notes

grafana/grafana (grafana)

v10.4.0: 10.4.0 (2024-03-06)

Download page
What's new highlights

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

v10.3.1

Compare Source

Bug fixes

v10.3.0: 10.3.0 (2024-01-22)

Compare Source

Download page
What's new highlights

To resolve a technical issue within the Grafana release package management process, we are releasing both Grafana 10.3.0 and Grafana 10.3.1 simultaneously. The 10.3.1 release contains no breaking or functional changes from 10.3.0. Please refer to the What’s New post for Grafana 10.3.0 for details on new features and changes in this release.

Features and enhancements
Bug fixes
Breaking changes

Users who have InfluxDB datasource configured with SQL querying language must update their database information. They have to enter their bucket name into the database field. Issue #​79579

Removes NamespaceID from responses of all GET routes underneath the path /api/ruler/grafana/api/v1/rules - 3 affected endpoints. All affected routes are not in the publicly documented or stable marked portion of the ngalert API. This only breaks clients who are directly using the unstable portion of the API. Such clients should use NamespaceUID rather than NamespaceID to identify namespaces. Issue #​79359

v10.2.0: 10.2.0 (2023-10-24)

Compare Source

Download page
What's new highlights

Features and enhancements

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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from mkilchhofer as a code owner October 15, 2025 17:32
@renovate renovate bot changed the title chore(deps): update grafana to v10.1.1 chore(deps): update grafana to v10.1.2 Oct 18, 2025
@renovate renovate bot force-pushed the renovate/grafana-monorepo branch from 523a6b7 to eaffdbc Compare October 18, 2025 17:04
@renovate renovate bot force-pushed the renovate/grafana-monorepo branch from eaffdbc to 4bfe87a Compare October 30, 2025 03:59
@renovate renovate bot changed the title chore(deps): update grafana to v10.1.2 chore(deps): update grafana to v10.1.4 Oct 30, 2025
@renovate renovate bot force-pushed the renovate/grafana-monorepo branch from 4bfe87a to 57a8ac8 Compare November 19, 2025 21:28
@renovate renovate bot changed the title chore(deps): update grafana to v10.1.4 chore(deps): update grafana to v10.1.5 Nov 19, 2025
@renovate renovate bot force-pushed the renovate/grafana-monorepo branch from 57a8ac8 to d6e1300 Compare November 21, 2025 14:32
@renovate renovate bot changed the title chore(deps): update grafana to v10.1.5 chore(deps): update grafana to v10.2.0 Nov 21, 2025
@renovate renovate bot force-pushed the renovate/grafana-monorepo branch from d6e1300 to fff8d12 Compare December 1, 2025 18:05
@renovate renovate bot changed the title chore(deps): update grafana to v10.2.0 chore(deps): update grafana to v10.3.0 Dec 1, 2025
@renovate renovate bot force-pushed the renovate/grafana-monorepo branch from fff8d12 to 79dd463 Compare December 11, 2025 16:27
@renovate renovate bot changed the title chore(deps): update grafana to v10.3.0 chore(deps): update grafana to v10.3.1 Dec 11, 2025
@renovate renovate bot force-pushed the renovate/grafana-monorepo branch from 79dd463 to 3aee384 Compare December 17, 2025 15:14
@renovate renovate bot changed the title chore(deps): update grafana to v10.3.1 chore(deps): update grafana to v10.3.2 Dec 17, 2025
@renovate renovate bot force-pushed the renovate/grafana-monorepo branch from 3aee384 to 678d97a Compare December 18, 2025 12:52
@renovate renovate bot changed the title chore(deps): update grafana to v10.3.2 chore(deps): update grafana to v10.4.0 Dec 18, 2025
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.

1 participant