chore(repo): add automated dev releases #14
Merged
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.
What is the current behavior?
We don't have any support for automated dev builds.
While this may seem unneeded for a new project, it's a great way to allow us to get quick feedback from the community, and build towards automated production deployments
GitHub Issue Number: N/A
What is the new behavior?
add the ability to publish a dev build of the project to the npm registry. we do so by adding a new workflow that can be manually kicked off,
release-dev
. as the name implies, it creates a dev build (running the most basic/essential parts of the build pipeline) and invokes a publish to npmDocumentation
Does this introduce a breaking change?
Testing
In 7fde790, I had a push event trigger enabled such that when I pushed this branch to GitHub, a dev build would get triggered. I considered this to be safe because:
Other information