Replies: 2 comments
-
|
Beta Was this translation helpful? Give feedback.
0 replies
-
We discussed this on a call. What we're landing on is:
In this set up we will have 2 NPM release channels:
And we will also want a
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
An automated NPM publish by a Github action when merging to the
main
branch with aprerelease
version (+ commit SHA) on a specific NPM dist tag. Makes sense to use a similar version format Lerna is using for this since we use this in Mux elements. See link below.The added commit hash (SHA) is useful because CI/CD runs possibly in parallel, multiple people w/ several feature branches -> avoid version collisions.
Handy resources:
Question 1: See below interactive poll ⬇️
Question 2: What should the NPM dist tag (release channels) be called?
Please answer with comment
Question 3: Should we also do this for Pull Requests?
If yes, please answer yes with answers for question 1 (prerelease tag?) & 2 (dist tag?)
Question 4: Should there be a manual GH action trigger for a normal release?
2 votes ·
Beta Was this translation helpful? Give feedback.
All reactions