-
Notifications
You must be signed in to change notification settings - Fork 10
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: ink v5.1 #409
chore: ink v5.1 #409
Conversation
422a61b
to
0419035
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
@@ Coverage Diff @@
## main #409 +/- ##
=======================================
Coverage 68.41% 68.41%
=======================================
Files 70 70
Lines 11838 11838
Branches 11838 11838
=======================================
Hits 8099 8099
Misses 3482 3482
Partials 257 257 |
Should we use git path to latest main branch then? |
Why? |
To avoid updating the version every time there's a new update. Anyway, this could brings unexpected issues so ignore my comment. |
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! Contracts compiled and built.
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.
Everything looks great! I tested deploying a smart contract and interacting with it, and everything is working perfectly.
In v5.0 there was an ugly warning from the linter which is fixed in v5.1. Also good to uplift the version.