-
Notifications
You must be signed in to change notification settings - Fork 796
feat: use Grafana 11.6.1 to fix issues when using browser locale for date formats #4662
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
Conversation
✅ Deploy Preview for teslamate ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
The |
Release has not happened yet - in contrast to what has been stated in the docs https://grafana.com/docs/grafana/latest/upgrade-guide/when-to-upgrade/#when-to-expect-releases Let's wait and see, it will happen. |
143e27d
to
95941b3
Compare
ac83534
to
527d2ca
Compare
527d2ca
to
6f3d922
Compare
11.6.1 released, PR updated, fix for #4657 not included yet, will update tomorrow, afterwards ready to be merged and released 🚀 |
… obsolete config entries
What about "Workaround for Grafana Issue #89777, fixed in 11.6.0 via #101391, extra layer to be removed on broad availability of 11.6.0" |
11.6.0 is not yet available in nixos stable, therefore left it in - to be removed in may? |
Ah, got it and makes sense. Currently testing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm and succesfully tested all dashbords
ty |
fixes #4656, fixes #4657, fixes #4690