-
-
Notifications
You must be signed in to change notification settings - Fork 934
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve release process #4934
Comments
It seems that publishing on CI (GitHub Actions) is now available via automation token: https://github.blog/changelog/2020-10-02-npm-automation-tokens/ By this feature, I expect we can realize the complete automation of npm publishing! |
Labelling as "ready to implement" if someone wants to investigate how this might work. |
Another write-up on using GitHub Actions: |
@jeddy3 did you close this issue on purpose? |
Oops! Nope, I didn't mean too. |
This issue is older than one month. Please ask before opening a pull request, as it may no longer be relevant. |
The changesets workflow is not used fully for now, for example, auto releasing on CI. I'm not for sure is there anything blocks us from migration. |
#7473 was related |
There are also actions to create GitHub releases. |
Our release process has served us well over the years, but it has quite a few manual steps. We should revisit it as we're trying to reduce the friction to publishing contributions.
@ntwb suggested:
There’s quite a few GitHub Actions that can publish to npm, there’s a list here:
https://github.com/marketplace?type=actions&query=Npm+pub
The ones i've looked at work like this:
Setting this up for the stylelint organisation would greatly simplify the release process for all repos IMHO
A few changes to the workflow would be required, primarily the change log update, but I think that shouldn’t be too tricky to overcome
There is also PR: #4682, which is of a similar vane.
I'm labelling as "discussion" so that everyone can, if you like, share their ideas and thoughts on how we can make the release process better.
The text was updated successfully, but these errors were encountered: