-
Notifications
You must be signed in to change notification settings - Fork 75
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
chore!: update dependencies #814
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #814 +/- ##
==========================================
+ Coverage 85.01% 85.03% +0.01%
==========================================
Files 84 84
Lines 20656 20656
Branches 20656 20656
==========================================
+ Hits 17561 17565 +4
+ Misses 2228 2226 -2
+ Partials 867 865 -2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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, but is this a chore!
that needs breaking-change
label?
thanks, sorry should have been more specific here - i've updated PR description with more details, but TLDR no, i don't think so |
actually, due to cargo's dependency resolution i suppose upgrading any dependencies' major version is a breaking change..? |
title, minimal changes to integrate some breaking changes. note that this is not a breaking change for kernel since the types from crates with breaking changes never escape the kernel.
breaking updates (remaining updates are all non-breaking):
EnumProperties
which we don't use.