Bump morley
Description
Problem: there were breaking changes in morley and lorentz, now we have to update the code respectively.
Solution: do bump.
Related issue(s)
Resolves #
![:white_check_mark: :white_check_mark:](/-/emojis/4/white_check_mark.png)
Checklist for your Merge Request
![:white_check_mark: :white_check_mark:](/-/emojis/4/white_check_mark.png)
Related changes (conditional)
-
Tests (see short guidelines)
-
If I added new functionality, I added tests covering it. -
If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.
-
-
Documentation
Stylistic guide (mandatory)
-
My commits comply with the following policy. -
My code complies with the style guide.
Merge request reports
Activity
added 7 commits
-
b72eccce...aabaaa87 - 5 commits from branch
master
- 77daff0c - Bump over #512-nested-storage-access of lorentz
- fd1a9c1a - Add tests in StoreClass instances
-
b72eccce...aabaaa87 - 5 commits from branch
added 2 commits
@pasqu4le Seems ready.
From Slack:
- either merge docs/upgradeableContracts.md into the README or include it into the extra-source-files (maybe the former makes more sense?)
I think the scope of the repository is yet broader than
upgradeableContracts.md
document, and this document rather serves as a suggestion and may not match the implementation. We better fillREADME
separately.- Resolved by Pinto Pasquale
Only one comment, also I think that the message for d3cbd49c contains a typo and should probably be reworded a bit.
marked this merge request as draft from 332ddfe5
added 3 commits
added 2 commits
enabled an automatic merge when the pipeline for f046c86a succeeds
mentioned in commit 202ca74c
@pasqu4le Letting you push the tag and upload the package to hackage since I'm not sure which practices to follow here :nate: