added release workflow #421
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
|
Ok, looking in the right direction. Can you change the zip of the codebase name to be something more like "open5e-api-1.1.1.zip" or something? I also think DRAFTING the release is probably a good idea, so I think the process would roughly be: |
|
Ah, sorry, remote the build step as well, I'm imagining literally just code (for now) is part of our release. There's no way at the moment to really use open5e as a dependency. |
coderatul
commented
Mar 8, 2024
augustjohnson
approved these changes
Mar 8, 2024
|
We'll test this out with 1.5.0 |
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.
don't know whether it would work or not because to check build has to run whihc needs docker credentials