semantic-release

@SemanticRelease

📦🚀 fully automated package publishing

CI
semantic-release.gitbook.io/semantic-relea…
Joined September 2017
1 Photo or video Photos and videos

Tweets

You blocked @SemanticRelease

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @SemanticRelease

  1. Retweeted
    Jul 30

    My series "Semantic Release Automation" is now added to resources section.

    2 replies 1 retweet 4 likes
    Undo
  2. Jun 14

    🌟 10.000 stars on 🌟

    9 retweets 55 likes
    Undo
  3. Apr 13

    📯 ProTip™: Use open ended ranges for "peerDependencies" in your package.json, just like you do for "engines"

    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.
    1 reply 6 retweets 19 likes
    Undo
  4. Apr 8

    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 ' LTS release schedule relates to package maintainers:
    2 retweets 5 likes
    Undo
  5. Retweeted
    Mar 19

    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 and Actions to automate npm package publishing.

    5 retweets 15 likes
    Undo
  6. Retweeted
    Feb 20

    Thanks to everyone who helped test the beta and pre-releases. Special shout out to that makes the process of beta releases ➡ next releases ➡ stable release a piece of cake 🍰💘

    1 reply 2 retweets 6 likes
    Show this thread
    Show this thread
    Undo
  7. Retweeted
    Feb 17
    Replying to

    We adopted at project recently. I can't be happier about release workflow we've got. You can use our repos as an example of the Python project released continuously.

    1 reply 1 retweet 1 like
    Undo
  8. Jan 12

    Wombat Dressing Room, a 2FA proxy for npm 🎉 automate publishing to npm, while keeping 2FA enabled; from our friends at :

    5 retweets 12 likes
    Undo
  9. Jan 10

    🎁 Happy new year: v16 is out! Our favorite new feature is support for maintenance & pre-releases: Big shoutout to maintainer who championed this new release! Thanks to everyone who contributed 💐

    2 replies 7 retweets 10 likes
    Undo
  10. Retweeted
    Jan 7

    🤔Should with "chore" or "docs" result in a new release? If yes -> Which version would you choose? If no -> How would you update your README on for example? Please answer in with a comment 😉

    2 replies 1 retweet 1 like
    Undo
  11. 29 Nov 2019

    Postmortem: the deletion and recovery of semantic-release's main repository

    6 likes
    Undo
  12. Retweeted
    19 Jun 2019

    Finally after a long time I had time and the chance to contribute to again. Only a small fix for a of but now can get -messages for every new version ... Not necessary but fun 😎

    2 replies 3 retweets 9 likes
    Undo
  13. Retweeted
    10 Jun 2019

    🚀 Yes! New article! 💥 The ultimate guide to set up your library project! ✅ code formatting with & Husky ✅ coverage with ✅ deployed showcase with Pages ✅ automated releases with and

    1 reply 16 retweets 35 likes
    Undo
  14. Retweeted
    3 Jun 2019

    Did anyone try to setup to run actions? Or think that’d be a good idea? Please let me know! You can follow this issue for updates on that front:

    1 reply 2 retweets 7 likes
    Show this thread
    Show this thread
    Undo
  15. Retweeted
    13 Dec 2018

    🤯 I published a maintenance release, just by creating a "15.x" branch: Thanks v16.0.0-beta.3, learn more here: Outstanding work 👏👏👏

    2 replies 4 retweets 10 likes
    Show this thread
    Show this thread
    Undo
  16. 3 Dec 2018

    The semantic-release community is moving to ! 🎉 Join the conversation, ask for help or provide support to other users at

    8 retweets 15 likes
    Undo
  17. Retweeted
    30 Nov 2018

    ⚠️ If you used the CLI in the past and pressed the "always allow" button when asked for access to your keychain, you actually granted access to node itself, _any_ node app could steal your secrets. ⚠️

    1 reply 19 retweets 16 likes
    Show this thread
    Show this thread
    Undo
  18. Retweeted
    21 Nov 2018

    Changes to the master branch automatically create a new release of my ui library via and with autopublish to - my website and CV can then be updated with the push of a button using – in two languages of course thanks to react-i18next

    1 reply 3 retweets 2 likes
    Show this thread
    Show this thread
    Undo
  19. Retweeted
    16 Nov 2018

    It’s all automated using nightly cron jobs, & . Such a joy to wake up in the morning and everything got magically updated 🎩🤖

    2 retweets 6 likes
    Show this thread
    Show this thread
    Undo
  20. 27 Nov 2018

    Oh hi there repository release-only notifications

    You can now watch repository releases only. This is a really cool feature!
    1 reply 2 likes
    Undo

@SemanticRelease hasn't Tweeted yet.

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·