semantic-release

📦🚀 fully automated package publishing

Submit a tweet:

[Benedicte (Queen) Raae 👑 @raae]

I am thoroughly spoilt by automagical versioning, publishing, tagging and change logging courtesy of @SemanticRelease 🙏

[semantic-release @SemanticRelease]

🤖📯 semantic-release v18 is out!

Upgrade should be straight forward, we only dropped support for Node 10 + Node 12. Minimum required version is current Node 14 LTS.

Next up: ES Modules!

[semantic-release @SemanticRelease]

🐦💡 Did you know? You can submit tweets to @SemanticRelease using a pull request at https://t.co/RLPoiJiwoS

Wrote a tutorial? Gave a talk? Share it with us! It's as important a contribution as a new feature, documentation improvement, or responding to a question 💖

[Giannis Koutsaftakis @kouts_tweet]

Release tasks are soooo boring! Setup automated versioning and package publishing to @npmjs for your JavaScript project using @github Actions and @SemanticRelease. https://t.co/v8RZBAkE8y

[ברוך אודם @baruchiro]

In my projects, I struggle with the versions.

Automation will always be problematic because it will always have a non-intuitive part, with weird commit messages or keep the source synced with npm.

I wrote how to implement auto semantic release:

https://t.co/mVuvxjICeu

[semantic-release @SemanticRelease]

📯 semantic-release v18 is happening!

We are dropping support for Node 10 & 12, and will likely make it a native ES Module.

We need to upgrade the core plugins as part of that. Pull requests welcome 💝💐
https://t.co/yFC9iY5wbI

[Joris Kraak @joriskraak]

Interested in further, i.e. fully, automating the release process of your Julia packages?

Come listen to me talk at #JuliaCon, tonight 19:40 UTC, on using @SemanticRelease to make the entire release process a matter of merging to your 'main' branch!

https://t.co/BZq2XRyxFm

[Julien Bouquillon - revolunet @revolunet]

Python friends, you can now rely on
@SemanticRelease to automate your PyPi releases, changelogs and more 🎉

https://t.co/fHBUNpPjpw

[semantic-release @SemanticRelease]

@meghzz17 @pvdlg_ it's MIT licensed https://t.co/Wt0SuQ6bfz

[semantic-release @SemanticRelease]

🤖 Oopsie

[Mathias Raacke - oocx.bsky.social @oocx]

If you are using "x.x.x-hash" as @SemanticRelease version for helm, it will fail if the hash starts with a 0 and has digits only (which is correct, it is not a valid semver version).

The probability for such a 7 digit hash is something like 0.0013%.

Guess how I know... 🙄

[semantic-release @SemanticRelease]

@line_o @duncdrum 🕺🏾🤖💃🏾

[semantic-release @SemanticRelease]

@gempain same same 😊

[semantic-release @SemanticRelease]

@gempain 👊🤖

[semantic-release @SemanticRelease]

📯 Kubernetes friends: you can now manage your @HelmPack charts with semantic-release:

https://t.co/5vQSngDsdF

[semantic-release @SemanticRelease]

@kbariotis We don't support 0.x.x releases, we recommend per-releases (e.g. 1.0.0-beta.1, etc) instead:

https://t.co/NOqPLisa8B

[semantic-release @SemanticRelease]

🤖📯 Behold humans! I now got the power to upload packages to PyPI.

https://t.co/AmP9B4OF80

[Nathan Friend @NathanAFriend]

Wrote up a tutorial about using @SemanticRelease to automatically publish NPM packages to the @GitLab Package Registry: https://t.co/qINYu4d5vi

[semantic-release @SemanticRelease]

📯 semantic-release release now works with the new npm automation tokens. That means you can enable two-factor auth on your account, while still automating releases through CI.

Thanks for confirming @grantila @hamzahamidii @thenieds

https://t.co/gaHAa08jXB

[Ahmad Nassri @AhmadNassri]

if you're using @SemanticRelease + @nodejs 15 or @npmjs >=7.0.5 you're gonna have a bad time:

PSA here so you don't waste hours of your life chasing the issue like I did: https://t.co/qNM7OPAOxw

[semantic-release @SemanticRelease]

@kentcdodds @MichaelDeBoey93 @tannerlinsley "next" works different, it won't release pre-releases with a "-next.1" suffix in the version, it will publish the calculated version, but instead to @latest, it will use the @next dist-tag. When you merge the branch, it will only update the dist-tag, not create a new version