Lesson 13: upgradeTo is deprecated .. again #1033
sunnyStefi
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
Amazing @sunnyStefi, can you send a PR to the Chronological updates? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hei coders!
It's super awesome that openzeppelin is updating their contracts every few months 😮 ! But this gives us always the downgrading version problem, that's not really a solution, isn't it? 🙈 🙉 🙊 We already moved from
version 4
toversion 5
!Since we are using just few libs, it would be awesome to have the course coded checked and updated (at least on github) whenever openzeppelin or others release a new version.
ref Openzeppelin docs
Major Releases
Major releases should be assumed incompatible. Nevertheless, the external interfaces of contracts will remain compatible if they are standardized, or if the maintainers judge that changing them would cause significant strain on the ecosystem.
An important aspect that major releases may break is "upgrade compatibility", in particular storage layout compatibility. It will never be safe for a live contract to upgrade from one major release to another.
This happened already with the ERC20Mock constructor, now with the
upgradeTo
in place ofupgradeToAndCall
insideUUPSUpgradeable.sol
.It looks like a recurrent problem. We, as community can help for sure with a push but maybe it would be more helpful just to have an actualised code on github?
Beta Was this translation helpful? Give feedback.
All reactions