CI: Automate release workflow #102
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
[why] Releasing is too hard. [how] The maintainer needs to set a new version in the package.json. Afterwards the release draft creator can be manually triggered on the Actions tab of the Github repo. This will draft a release with a new font generated from the current vectors. And the current commit will be git tagged with the release version. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
I imitated the contents of the release v1.0.1 files. Not sure that all that files are really useful. Otoh do not know if this npm thing need it. |
|
Just noticed that the files are not automagically compressed.
|
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
Ok, this seems ready. I tested everything except the final publish-to-npm. Will try to use the workflow to get |
|
Test on v1.0.1, success:
|
|
Actual assets missing?? Working on it...
|
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.
[why]
Releasing is too hard.
[how]
The maintainer needs to set a new version in the package.json. Afterwards the release draft creator can be manually triggered on the Actions tab of the Github repo.
This will draft a release with a new font generated from the current vectors. And the current commit will be git tagged with the release version.
Fixes: #29