Autopublish npm packages every week - #1542
Merged
Merged
Conversation
Collaborator
Collaborator
Author
|
@mho22 not intended at all, that's a bug and we should fix it – thank you for reporting |
Collaborator
|
@adamziel There seems to be an issue on line: |
Collaborator
Author
|
Yes please, thank you @mho22 ! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Motivation for the change, related issues
Publishes Playground packages every week to enable integrators to stay on top of the latest changes.
The manual "publish when needed" approach we've used so far is no longer suitable. It was based on an assumption that the most interested developers will keep up with the project and ask for a new release when needed. In reality people tend to keep up with the npm packages, not the GitHub repo. A few developers reached out and directly asked for more frequent releases.
This PR ensures there's a patch release every Monday. Let's see how well it works and continue iterating on the approach should any problems arise. In the future, we might want to explore formal release trains, beta periods, and such, but today I believe we can get away with a much leaner approach.