You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use the Grafana dashboard linter in many of our CI's to ensure we keep a consistent quality level in our dashboards.
The project is not tagged at the moment, leading us to point to the @latest version of the go package.
Impact
This resulted in all of our CI's that use the grafana dashboard linter to fail this week because of a breaking change in the linter (addition of logql rules). While this change is welcomed, it should have been associated with a new version of the project, and we could have made this change on its own.
Description
We use the Grafana dashboard linter in many of our CI's to ensure we keep a consistent quality level in our dashboards.
The project is not tagged at the moment, leading us to point to the
@latest
version of the go package.Impact
This resulted in all of our CI's that use the grafana dashboard linter to fail this week because of a breaking change in the linter (addition of logql rules). While this change is welcomed, it should have been associated with a new version of the project, and we could have made this change on its own.
Reference
GitHub action workflow
The text was updated successfully, but these errors were encountered: