ci: implement release of aos modules #323
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
TillaTheHun0
force-pushed
the
peterfarber/wasm-workflows
branch
4 times, most recently
from
4155476
to
dd90c4c
Compare
TillaTheHun0
force-pushed
the
peterfarber/wasm-workflows
branch
from
dd90c4c
to
786e0f8
Compare
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.
This PR implements the initial release job for
aos. It can be triggered via a workflow dispatch and will perform the following:aosand upload as workflow artifactaos.wasmaos-sqlitemodule and upload as workflow artifactaos-sqlite.wasmaos-llamamodule and upload as workflow artifactaos-llama.wasmEventually, we can the modules automatically upload to Arweave, and update manifest files with new versions/tx ids for use in the console.