Release Workflow #7
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
|
I'm onboard with it, cc @jlsnow301 |
|
Approve, but there are still some linter failures around Byond not being defined. Might be able to disable this explicitly for the byond object |
|
i guess this should also update npm |
jlsnow301
approved these changes
Aug 8, 2024
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.
A workflow to automagically build, generate, and publish new releases
Use is documented in the README. Should be fairly simple, you just create an empty release with the version you want as a tag and it set to the latest commit. The action will fill out the release details, which you could edit after if you wanted.
Ends up looking somewhat like this, after publishing a release targeting that merge commit:
For Merge:
Need to create a repository secret named
NPM_TOKENwith the npm push token in it.After Merge:
I guess we should formalize not pushing built dist files? Maybe a precommit hook?