Draft: Testing how to automate releases #69
Draft
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 is a draft PR demonstrating how we can use semantic-release to automatically publish releases for this repository.
How to Test
cd
into it.git pull && git checkout ruetz-automate-releases
.This PR can be tested in two ways:
Locally
GITHUB_TOKEN
.repo, workflow, write:packages
scopes.ghp_...
token value.ghp_...
with the resulting token value from Step 2):act -s GITHUB_TOKEN=ghp_...
Release
job logs, verify that the resulting version number is bumped (as of this writing the latest release isv2.0.0
; in my testing the next version results inv2.1.0
).CI/CD
ruetz-automate-releases
branch.git push
it up to the remote.Release
job logs, verify that the resulting version number is bumped (as of this writing the latest release isv2.0.0
; in my testing the next version results inv2.1.0
).