You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using semantic release for a while in someofmyprojects to automate the release process and I think it would be of value to add it to this project too.
Their docs go through the advantages of this approach, but I'll highlight a few that I think are important (as well as some potential drawbacks).
Advantages
Release process is defined in code (thus easily done)
No reliance on individuals to find time to make releases and no single point of failure for releases
Much less error prone (no room for human error when making a release)
We can use GitHub actions to perform package attestation (provenance) - this can't be done on local machines and has to be in CI
Quickly release features/fixes when merged
Automate tedious and easily missed elements like changelog generation
Disadvantages
Requires we adopt commit conventions so that the CI process can determine when to make a release and what kind of release to make (typically conventional commits is used) - this may be a good thing depending on your point of view
Can lead to large number of releases
Reviewers and contributors need to be aware that only working code can go into master and that their commit messages must be accurate.
I'm pretty familiar with the process, so happy to put the work in to integrate it. I will need someone to add some secrets to the GH repo to allow publishing to NPM (I don't need to know the secret, it just needs to be available to the runner when publishing), and we need to come to an agreement about what the release process should include. For example, if we want to include changelog generation, then the CI pipeline will need permission to push to master (or any other release branch).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi team.
I've been using semantic release for a while in some of my projects to automate the release process and I think it would be of value to add it to this project too.
Their docs go through the advantages of this approach, but I'll highlight a few that I think are important (as well as some potential drawbacks).
Advantages
Disadvantages
master
and that their commit messages must be accurate.I'm pretty familiar with the process, so happy to put the work in to integrate it. I will need someone to add some secrets to the GH repo to allow publishing to NPM (I don't need to know the secret, it just needs to be available to the runner when publishing), and we need to come to an agreement about what the release process should include. For example, if we want to include changelog generation, then the CI pipeline will need permission to push to
master
(or any other release branch).Beta Was this translation helpful? Give feedback.
All reactions