OpenZeppelin / OpenZeppelin/openzeppelin-upgrades
Automatically run tests on new Solidity releases
Open
Nobody has claimed this yet.
tests
- Dominant language
- TypeScript
- Stars
- 658
- Forks
- 286
- PR merge metrics
- No merged PRs in 30d
Description
We're not detecting potential issues with new Solidity releases such as #169.
Some potential ways to do this:
- Always compile with the latest Solidity version. It may not be desirable to always ship contracts compiled with different versions. Among other things, each new version would require separate verification on Etherscan. However, see #164.
- Trigger a test run with every new Solidity release.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review issue #169 for the reported release-related problem and issue #164 for the alternative approach. Determine how new Solidity releases should trigger the test suite without changing the versions used for shipped contracts; done means those releases are tested automatically and potential compatibility issues are detected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity
- Domain
- blockchain, ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100