⬆️ Update grafana/grafana to v10.3.1 #382
Merged
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:
v10.2.3
->v10.3.1
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
grafana/grafana (grafana/grafana)
v10.3.1
: 10.3.1 (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.
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 #79579Removes
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 orstable
marked portion of the ngalert API. This only breaks clients who are directly using the unstable portion of the API. Such clients should useNamespaceUID
rather thanNamespaceID
to identify namespaces. Issue #79359Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.