semantic-release retweeted
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 github.com/semantic-release/…
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 💖
semantic-release retweeted
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/automated-versi…
semantic-release retweeted
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:
medium.com/@baruchiro/how-to…
📯 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-release/…
semantic-release retweeted
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/CY88Q…
semantic-release retweeted
Python friends, you can now rely on
@SemanticRelease to automate your PyPi releases, changelogs and more 🎉
npmjs.com/package/semantic-r…
🤖 Oopsie
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... 🙄
📯 Kubernetes friends: you can now manage your @HelmPack charts with semantic-release:
npmjs.com/package/semantic-r…
🤖📯 Behold humans! I now got the power to upload packages to PyPI.
npmjs.com/package/semantic-r…
semantic-release retweeted
Wrote up a tutorial about using @SemanticRelease to automatically publish NPM packages to the @GitLab Package Registry: docs.gitlab.com/ee/ci/exampl…
📯 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-1…
semantic-release retweeted
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-release/…
👋🤖 Please welcome @mtravi, the the latest additions to my maintainer humans. beep boop
semantic-release retweeted
My series "Semantic Release Automation" is now added to
@SemanticRelease resources section.
github.com/semantic-release/…
📯 ProTip™: Use open ended ranges for "peerDependencies" in your package.json, just like you do for "engines"
xitter.cf/boenneman…
Replying to @rfgamaral
I would recommend to always use open ended ranges. E.g. "graphql": ">=14". Just like you would use `engines.node`. Basically only exclude what you know is broken and don't make guesses about the future.
This is a great read by Ben: How Node's LTS release schedule relates to package maintainers
I wrote an article about how I think @nodejs' LTS release schedule relates to package maintainers:
medium.com/the-node-js-colle…
semantic-release retweeted
Version numbers need not be sentimental! Use semantic commit messages and let the robots choose the version numbers.
Here's a video showing how to use @SemanticRelease and @github Actions to automate npm package publishing.
youtube.com/watch?v=rCXq86FO…













