Twitter | Search | |
swyx ⚛️ @ReactRally
Do you automate releases from GitHub to npm? A bit like “continuous deployment for libraries”. What’s the best way to do this? (Assuming we have faith in our tests)
Reply Retweet Like More
John Reilly Apr 18
Replying to @swyx
I'm liking the GitHub actions approach:
Reply Retweet Like
swyx ⚛️ @ReactRally Apr 18
Replying to @johnny_reilly
oh i may need to do exactly this! is Actions in general availability? i’m not aware if i have access
Reply Retweet Like
Sasha 🐑💨 Koss Apr 18
Replying to @swyx @date_fns
Here's the script that does the job:
Reply Retweet Like
swyx ⚛️ @ReactRally Apr 18
Replying to @kossnocorp @date_fns
wow you even tweet the release?! baller i like how you echo the auth token into npmrc. i’ll definitely need that if i go down this path. have you seen the GH actions approach? looks pretty clean. no filter by tag tho
Reply Retweet Like
Sasha 🐑💨 Koss Apr 18
Replying to @swyx @date_fns
No didn't look into it. I'm pretty happy with the current approach, and honestly, I'm afraid to change anything as it works like a clock.
Reply Retweet Like
swyx ⚛️ @ReactRally Apr 18
Replying to @kossnocorp @date_fns
yup absolutely. if it aint broke dont fix it
Reply Retweet Like
Satyajit Sahoo Apr 18
Replying to @swyx
semantic-release or configure release-it on ci
Reply Retweet Like
:party-corgi: Apr 18
Replying to @swyx
I ship every merge to master as the `ci` tag for gatsby-mdx using a lerna one-liner. Stable releases are manual though
Reply Retweet Like
Ari Palo Apr 18
Replying to @swyx
Yes Github+Travis: 🔀Branch prefix ”feature/”: Tag: branch name Version: previous tag & branch name as prerelease + build info 🔀Master branch commit: T: staging V: prev tag + ”staging” prerelease + build info 🔀Github release (tagged commit): T: latest V: major.minor.patch
Reply Retweet Like
swyx ⚛️ @ReactRally Apr 18
Replying to @satya164
seen both these packages before and i didn’t really have to implement it until now. thank you!
Reply Retweet Like
swyx ⚛️ @ReactRally Apr 18
Replying to @chrisbiscardi
right, this feels like it offers the most control. it seems most people automate even the stable releases tho, from replies. quick way to get bug reports!
Reply Retweet Like
swyx ⚛️ @ReactRally Apr 18
Replying to @aripalo
oh wow, the branch thing sounds like a good idea! so many good ideas people have.
Reply Retweet Like
Justin Bennett Apr 18
Replying to @swyx @orta
We use a tool called auto. . It does releases per PR with the versions being based on labels. Works for us a lot better than semantic-release did. wrote a blog post on it: . You can see it in action on
Reply Retweet Like
swyx ⚛️ @ReactRally Apr 18
Replying to @Zephraph @orta
amazing! many options. also idk how i wasnt following you i am pretty sure i followed you ages ago. fixed
Reply Retweet Like
Paulo Cunha Apr 18
Replying to @swyx
We've been using semantic-release in all our new libs, and it has been great! Here's an example of something set up with it:
Reply Retweet Like
swyx ⚛️ @ReactRally Apr 18
Replying to @pmrcunha
thanks! im gonna write up all the great responses i got here 🙇🏻
Reply Retweet Like
Jon Wong @ React Rally Apr 18
thank you for writing up the release guide - i’ve been wanting to do this for a while using semantic-release but was trying to figure out the other parts to get the integration off the ground!
Reply Retweet Like
swyx ⚛️ @ReactRally Apr 18
also check the latter half of Kent’s course here
Reply Retweet Like
Brian Douglas Apr 19
Replying to @swyx
GitHub Actions . Let me know if you need access
Reply Retweet Like