Skip to content
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

Open
jeddy3 opened this issue Sep 13, 2020 · 9 comments
Open

Improve release process #4934

jeddy3 opened this issue Sep 13, 2020 · 9 comments
Labels
status: ask to implement ask before implementing as may no longer be relevant type: infrastructure an improvement to devops

Comments

@jeddy3
Copy link
Member

jeddy3 commented Sep 13, 2020

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:

  • Create a branch, e.g release-17-8-0 and the action only fires if the branch name matches a regex
  • Once the tests pass, and once the PR is approved and merged, it publishes after merge to npm

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.

@jeddy3 jeddy3 added type: infrastructure an improvement to devops status: needs discussion triage needs further discussion labels Sep 13, 2020
@ybiquitous
Copy link
Member

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!

@jeddy3
Copy link
Member Author

jeddy3 commented Oct 11, 2020

Labelling as "ready to implement" if someone wants to investigate how this might work.

@jeddy3 jeddy3 added status: ready to implement is ready to be worked on by someone and removed status: needs discussion triage needs further discussion labels Oct 11, 2020
@jeddy3
Copy link
Member Author

jeddy3 commented Nov 15, 2020

Another write-up on using GitHub Actions:
https://snyk.io/blog/github-actions-to-securely-publish-npm-packages/

@jeddy3 jeddy3 closed this as completed Nov 15, 2020
@hudochenkov
Copy link
Member

@jeddy3 did you close this issue on purpose?

@jeddy3
Copy link
Member Author

jeddy3 commented Nov 15, 2020

Oops! Nope, I didn't mean too.

@jeddy3 jeddy3 reopened this Nov 15, 2020
Copy link
Contributor

This issue is older than one month. Please ask before opening a pull request, as it may no longer be relevant.

@github-actions github-actions bot added status: ask to implement ask before implementing as may no longer be relevant and removed status: ready to implement is ready to be worked on by someone labels Jan 22, 2024
@JounQin
Copy link
Member

JounQin commented Jan 22, 2024

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.

@Mouvedia
Copy link
Member

Mouvedia commented Feb 4, 2024

#7473 was related

@Mouvedia
Copy link
Member

There are also actions to create GitHub releases.
e.g. https://github.com/softprops/action-gh-release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: ask to implement ask before implementing as may no longer be relevant type: infrastructure an improvement to devops
Development

No branches or pull requests

5 participants