-
Notifications
You must be signed in to change notification settings - Fork 12
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 backend packages #180
Conversation
Backend code coverage report for PR #180 |
Frontend code coverage report for PR #180 |
Levitate is-compatible report: 🔍 Resolving @grafana/data@latest... 🔬 Checking compatibility between ./src/module.ts and @grafana/data@9.4.7... 🔬 Checking compatibility between ./src/module.ts and @grafana/ui@9.4.7... 🔬 Checking compatibility between ./src/module.ts and @grafana/runtime@9.4.7... 🔬 Checking compatibility between ./src/module.ts and @grafana/e2e-selectors@9.4.7... ✔️ ./src/module.ts appears to be compatible with @grafana/data,@grafana/ui,@grafana/runtime,@grafana/e2e-selectors |
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.
Do we know why we needed the testdata changes?
Seems there was some change in the "experimental" package of github.com/grafana/grafana-plugin-sdk-go which generated the expected json response during the update to v0.159.0 So the re-generated expected response includes the change. Let me know if we're not comfortable just going with this; I believe it's not strictly necessary for me to update grafana-plugin-sdk-go. |
Closes https://github.com/grafana/oss-plugin-partnerships/issues/174