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

⬆️ Update grafana/grafana to v10.3.1 #382

Merged
merged 1 commit into from
Jan 24, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 23, 2024

Mend Renovate

This PR contains the following updates:

Package Update Change
grafana/grafana minor 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 #​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


Configuration

📅 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.


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

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added dependencies Upgrade or downgrade of project dependencies. no-stale This issue or PR is exempted from the stable bot. labels Jan 23, 2024
@frenck frenck merged commit 4216a29 into main Jan 24, 2024
23 checks passed
@frenck frenck deleted the renovate/grafana-grafana-10.x branch January 24, 2024 07:45
@github-actions github-actions bot locked and limited conversation to collaborators Jan 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Upgrade or downgrade of project dependencies. no-stale This issue or PR is exempted from the stable bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant