build(ci): introduce initial GitHub actions workflow #2
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
Closed
spike-rabbit
force-pushed
the
build/add-ci
branch
3 times, most recently
from
c5bdc76 to
597c18a
Compare
timowolf
approved these changes
Dec 23, 2024
|
@spike-rabbit Update the commit message. |
A simple release workflow that releases using semantic release.
spike-rabbit
force-pushed
the
build/add-ci
branch
from
597c18a to
a21144b
Compare
|
🎉 This PR is included in version 1.0.0-next.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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 simple workflow that lints, tests, build and optionally release based on semantic release.
Does almost all the changes requested in #1 except for including versions in the downloadable artifact.
Currently, the artifacts are just references to the tag of the release. If we decide that we must have the artifacts with versions, we
need put extra configuration and generate a zip file on our own which would consume extra space.
Therefore I am against doing this.
The npm packages will contain the version as those are updated by semantic release.