Try to build release workflow #44
Merged
Conversation
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
|
It builds now, yay! See https://github.com/osmosis-labs/mesh-security/releases/tag/v0.2.0-alpha.3 as an example |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Need an expert on GitHub actions.
I want to port this logic over: https://github.com/CosmWasm/cw-plus/blob/main/.circleci/config.yml#L536-L626
And am using https://trstringer.com/github-actions-create-release-upload-artifacts/ as a guide.
I can't figure out how to loop over all contracts, so right now, I just try to build one of them and see if I can get that to work, so hopefully someone can expand it
Update: that article recommended an obsolete action. I am trying out https://github.com/softprops/action-gh-release which seems maintained