Update grafana/grafana Docker tag to v10.4.19 #109
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:
10.0.3->10.4.19Release Notes
grafana/grafana (grafana/grafana)
v10.4.19Compare Source
Bug fixes
v10.4.18Compare Source
Bug fixes
v10.4.17Compare Source
Features and enhancements
Bug fixes
v10.4.16Compare Source
Features and enhancements
Bug fixes
v10.4.15Compare Source
Features and enhancements
Bug fixes
v10.4.14Compare Source
Bug fixes
v10.4.13Compare Source
v10.4.12Compare Source
Bug fixes
v10.4.11Compare Source
Bug fixes
v10.4.10Compare Source
Features and enhancements
Bug fixes
v10.4.9Compare Source
Features and enhancements
Bug fixes
v10.4.8Compare Source
Bug fixes
v10.4.7Compare Source
Bug fixes
v10.4.6Compare Source
Features and enhancements
ce0d024#90389, @yuri-tceretianBug fixes
v10.4.5: 10.4.5 (2024-06-21)Compare Source
Download page
What's new highlights
Bug fixes
v10.4.4: 10.4.4 (2024-06-13)Compare Source
Download page
What's new highlights
Bug fixes
v10.4.3: 10.4.3 (2024-05-13)Compare Source
Download page
What's new highlights
Features and enhancements
Bug fixes
resbeing accessed after it becomesnilinpromql_query.go. #85959, @adamyeatsautorefresh option when saving a dashboard. #85921, @bfmateiv10.4.2: 10.4.2 (2024-04-10)Compare Source
Download page
What's new highlights
Bug fixes
v10.4.1Compare Source
Bug fixes
v10.4.0: 10.4.0 (2024-03-06)Compare Source
Download page
What's new highlights
Features and enhancements
advancedDataSourcePickerfeature toggle. #81790, @Sergej-Vlasov}when{is inserted automatically. #80113, @harrymaurya05serve_from_sub_pathsetting. #80062, @simPodBug fixes
@grafana/lezer-logqlto0.2.3containing fix for ip label name. #82378, @ivanahuckova:. #82327, @ivanahuckovahttpClientProvider. #81814, @svennergr/_mappingrequests. #80970, @svennergr__sourceis log message field. #80804, @ivanahuckovaBreaking 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 #83726If you use an automated provisioning (eg, Terraform) for custom roles, and have provisioned a role that includes permission with action
alert.instances:readand some scope, you will need to update the permission in your provisioning files by removing the scope. Issue #82202The following breaking change occurs only when feature flag
nestedFoldersis 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 labelgrafana_folder.For example, the folder title is
Grafana / Folder. Currently the labelgrafana_folderwill contain the title as it is. If PR is merged - the label value will beGrafana \/ Folder.This can break notifications if notification policies have matches that match that label and folder. Issue #81214
PanelContext.onSplitOpenis removed. In the context of Explore, plugins should usefield.getLinksto get a list of data link models. Issue #80087The 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.12Compare Source
Bug fixes
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.