Release v0.2.0 Berlin #1090
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| [package] | ||
| name = "solang" | ||
| version = "0.2.0" | ||
| authors = ["Sean Young <[email protected]>"] | ||
| homepage = "https://github.com/hyperledger/solang" | ||
| documentation = "https://solang.readthedocs.io/" | ||
|
|
@@ -46,7 +46,7 @@ itertools = "0.10" | |
| num-rational = "0.4" | ||
| indexmap = "1.8" | ||
| once_cell = "1.10" | ||
| solang-parser = { path = "solang-parser", version = "0.2.0" } | ||
| codespan-reporting = "0.11" | ||
| phf = { version = "0.11", features = ["macros"] } | ||
| rust-lapper = "1.0" | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -116,17 +116,6 @@ node flipper.js | |
|
|
||
| ## Build for Substrate | ||
|
|
||
| Run: | ||
|
|
||
| ```bash | ||
|
|
@@ -156,8 +145,8 @@ Here is a brief description of what we envision for the next versions. | |
| | Solana SPL tokens compatibility | Completed | | ||
| | Parse and resolve inline assembly | Completed | | ||
| | Generate code for inline assembly | Completed | | ||
| | Support Solana's Program Derived Addresses | Completed | | ||
|
There was a problem hiding this comment. This is my Anchor PR #1034 There was a problem hiding this comment. #1034 should get merged in the next few days? It would be really nice to have There was a problem hiding this comment. I don't think the release needs to wait for this. There was a problem hiding this comment. Should I put this back to There was a problem hiding this comment. Hmm what do you think of There was a problem hiding this comment. I did put it under |
||
| | Support latest Substrate production target | Completed | | ||
|
|
||
|
|
||
| ### V0.3 | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| [package] | ||
| name = "solang-parser" | ||
| version = "0.2.0" | ||
| authors = ["Sean Young <[email protected]>"] | ||
| homepage = "https://github.com/hyperledger/solang" | ||
| documentation = "https://solang.readthedocs.io/" | ||
|
|
||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These files are built during release, so usually we update these after release (not ideal)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this work if first tag it and let the release job run? Since this is in the
test.ymlThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The release job is run in parallel to the test job, so it will work if we re-run it after the release job.
I don't know a way of making the test workflow depend on the release workflow, conditionally if there is a release workflow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed on todays standup, to achieve this the first step would be to split our CI workflows to separate
buildfromtestjobs, so that early stagebuildartifacts can be used for tests but also as release assets. A further improvement would be to use something like bazel to gain the ability to "run" the CI locally.But how should we proceed here, should we try it like this (with the re run) or should I undo these changes for a follow up (having it included here would be nicer IMO)?