-
Notifications
You must be signed in to change notification settings - Fork 6.3k
Do not use fork of openzeppelin anymore #5106
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
Conversation
|
Fails. |
|
Hey @axic, I noticed your build is failing because of the breaking changes introduced in 0.5.0 (e.g. the data location for certain types now being mandatory). I was actually tracking that in this OpenZeppelin PR, and we even have an issue for this whole thing: OpenZeppelin/openzeppelin-contracts#1211. What do you think about having a branch in OpenZeppelin that compiles using nightly builds, instead of you having to maintain your own fork? That way we could give you a hand maintaining, making sure the branch gets updated often to reflect the latest changes, and it'd also make it easier for us to upgrade to the latest version once its released. |
|
@nventuro that would be wonderful! Do you already have such a branch? |
|
I just created the |
|
Will you make the updates? You know about https://github.com/axic/openzeppelin-solidity/tree/solidity-050 do you? |
The problem is we haven't merged upstream changes to it for 3 months. We could do that, but I think merging these 2 new PRs will be faster. |
This comment has been minimized.
This comment has been minimized.
2e39333 to
58c153b
Compare
|
No reason to keep this open. |
|
Zeppelin has released their 0.5.0-compatible version: https://github.com/OpenZeppelin/openzeppelin-solidity/releases/tag/v2.1.1 Updating it here. |
|
This works now. |
Depends on OpenZeppelin/openzeppelin-contracts#1498