semantic-release

I am thoroughly spoilt by automagical versioning, publishing, tagging and change logging courtesy of @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!

🐦💡 Did you know? You can submit tweets to @SemanticRelease using a pull request at #readme" target="_blank" rel="nofollow noopener">github.com/semantic-relea… 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 💖

Release tasks are soooo boring! Setup automated versioning and package publishing to @npmjs for your JavaScript project using @github Actions and @SemanticRelease. dev.to/kouts/automate…

📯 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 💝💐 github.com/semantic-relea…

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! live.juliacon.org/talk/CY88QP

Python friends, you can now rely on @SemanticRelease to automate your PyPi releases, changelogs and more 🎉 npmjs.com/package/semant…

@meghzz17 @pvdlg_ it's MIT licensed github.com/semantic-relea…

Just curious amd noob question, @SemanticRelease is the overall library licenced and can we use the licence uploaded in the repo? I don't see the official tag on the repo. cc: @pvdlg_

🤖 Oopsie

@line_o @duncdrum 🕺🏾🤖💃🏾

.@duncdrum and I just set up @SemanticRelease for something (roaster) that has nodes but no JS. Well, only for automation. What a magnificent product! As flexible as a dancer 🕺🏽!

@gempain same same 😊

@SemanticRelease I still get excited when I see this, even years of using your tool 😍

@gempain 👊🤖

@SemanticRelease we're trending #1 Github repo for 2 days now. Does one of the contributors look familiar to you ? Fame on you 😉

📯 Kubernetes friends: you can now manage your @HelmPack charts with semantic-release: npmjs.com/package/semant…

@kbariotis We don't support 0.x.x releases, we recommend per-releases (e.g. 1.0.0-beta.1, etc) instead: #can-i-set-the-initial-release-version-of-my-package-to-0-0-1" target="_blank" rel="nofollow noopener">semantic-release.gitbook.io/semantic-relea…

@SemanticRelease 👋 when the package version (package.json) is set to 0.x.x and the commit message specifies a minor update, the commit analyzer outputs: > ℹ There is no previous release, the next release version is 1.0.0 How can I maintain the 0.x.x version? Thanks

🤖📯 Behold humans! I now got the power to upload packages to PyPI. npmjs.com/package/semant…

Wrote up a tutorial about using @SemanticRelease to automatically publish NPM packages to the @GitLab Package Registry: docs.gitlab.com/ee/ci/examples…

📯 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 github.blog/changelog/2020…

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: github.com/semantic-relea…

@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

@MichaelDeBoey93 @tannerlinsley @SemanticRelease Step 1: Make sure you build a "beta" branch #L27" target="_blank" rel="nofollow noopener">github.com/testing-librar… Step 2: Push to your "beta" branch Done: travis-ci.org/github/testing… I think it works with "next" as well.

Hey semantic-release twitter, how can I configure a `beta` branch to release a *prerelease* of the next major semver? Main branch is 2.x right now, I want beta branch to release 3.x.x-beta@beta Why is this so hard.