Use the branch name to create the release #108
Merged
Conversation
This file contains hidden or 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
Signed-off-by: James Sturtevant <[email protected]>
syntactically
approved these changes
Jul 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The previous step created a release on the wrong tag and version: https://github.com/hyperlight-dev/hyperlight-wasm/releases/tag/v0.8.0-preview.1. I've manually updated the release to reflect the correct tag but this will make it automated in the next release.
This updates the step to do the same thing the hyperlight repo does so we can follow the same process in this repo: https://github.com/hyperlight-dev/hyperlight/blob/39df600cbaf5a9a74215879f67207d1d07dc3d54/.github/workflows/CreateRelease.yml#L110-L117