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.
It's more reliable to generate releases via CI rather than a local build.
I've added Github actions that will generate a release draft with zip file attached when a tag like
v1.4.0
is pushed to the repository. It also generates and uploads release container to Docker hub.Details:
Before merging:
To publish to Docker hub, it requires
DOCKER_USERNAME
andDOCKER_TOKEN
to be set up. Just create account on docker hub, generate an access token, and then add 2 secrets in your repository settings.I've also added build status shields to readme, and included
package-lock.json
into release (it's highly recommended to do so, and also usenpm ci
to install packages on users machine)You can see CI in action in my fork poma/assistant-relay and pushed images on Docker hub