This repository has been archived by the owner on Oct 27, 2021. It is now read-only.
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.
Sorry for not being careful for the 1.0.0 releasing process. But I think we should not go back in version no just to get a clean 1.0.0 ... :-(
What I've improved:
The npm publish step requires a github-secret
NPM_TOKEN
.You can create this on npm in the Auth-Token section & you can store this on Github in project-settings / secrets.
You can test the process if you push a tag like '1.0.1-dev-0'.
It should look somehow like https://github.com/DomainDrivenArchitecture/mastodon-bot/runs/819574051?check_suite_focus=true#step:11:1
If everything is fine, we can remove the dry-run, tag again and enjoy our first ci-driven version in GH releases and on npm.