Alternative versions of 0.4.15, 0.5.9, 0.5.11 from github release page #57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the most important part of ethereum/solidity#7512. The PR adds releases from github for versions where the file in this repository was not actually built on the release tag.
Files were downloaded and renamed using my script from #41. The name is based on the commit associated with the tag and there's nothing preventing the file in the release from having been actually built on a different commit so I manually checked versions reported by the executables using
solc-js
. They all match the name:version()
soljson-v0.4.15+commit.8b45bddb.js
0.4.15+commit.8b45bddb.Emscripten.clang
soljson-v0.4.15+commit.bbb8e64f.js
0.4.15+commit.bbb8e64f.Emscripten.clang
soljson-v0.5.9+commit.c68bc34e.js
0.5.9+commit.c68bc34e.Emscripten.clang
soljson-v0.5.9+commit.e560f70d.js
0.5.9+commit.e560f70d.Emscripten.clang
soljson-v0.5.11+commit.22be8592.js
0.5.11+commit.22be8592.Emscripten.clang
soljson-v0.5.11+commit.c082d0b4.js
0.5.11+commit.c082d0b4.Emscripten.clang