Matt Travi

DivOps engineer. Maintainer @SemanticRelease, repository-settings, form8ion. Co-lead @desmoinesjs

[Matt Travi @mtravi]

@burgessdryan YUI, then jQuery

[Home Assistant @home_assistant]

Yes, we did a One More Thing during #HA10… 💚 Home Assistant Green is our new affordable smart home hub. It’s designed to be the easiest way for everyone to start with Home Assistant, for just $99.

[Node.js @nodejs]

⚠️ Node.js 16 is now end of life, please upgrade to Node.js 18.

Details: https://t.co/k4WVTMejMZ

[OpenSauced @saucedopen]

🎙️ New episode! Dive into the magic of #opensource with @github's @gr2m & @bdougieYO from OpenSauced. From Hoodie to Greenkeeper, learn about Gregor's journey & the power of GitHub apps. Tune in and enjoy! 🔥 #github #opensource

[Matt Travi @mtravi]

@jcreamer898 Have you covered ;)

https://t.co/ydwKh6jWYT

[Artem Zakharchenko @kettanaito]

This 👇
If you're on Node 14 you are in danger. If you're on Node 16 you're about to be.

Migrate to Node 18, please.

[EFF @EFF]

Looking for a weekend project? Build your own privacy-respecting smart home hub. https://t.co/by8cGevCBt

[Dan Lorenc @lorenc_dan]

Wow, over 1000 @npmjs packages have already enabled the @projectsigstore based provenance: https://t.co/3ardkbxor9

[Mend.io @Mend_io]

🔋 Powered by data from Renovate, we’re introducing our inaugural edition of the https://t.co/zX0yVYaspv Open Source Reliability Leaderboard. The full report showcases detailed rankings for npm, PyPi, and Maven. Check out our latest blog ➡️ https://t.co/dfXxuLv1PW
#MendTogether

[Matt Travi @mtravi]

@liran_tal @_rafaelgss And @renovatebot does a great job both doing the pinning and keeping them up to date like https://t.co/gIAL3gMf8s

[Matt Travi @mtravi]

@jplhomer @little_bret Yep, my address/postal code is Cumming, IA but I'm in the city limits of Norwalk, IA

[Matt Travi @mtravi]

@liran_tal thanks a lot. really appreciate the contributions 😀

here are a couple of items that have had my attention lately that you might also be interested in:
* https://t.co/pyHAj1LhVN
* https://t.co/k1FfdBgrHH

[Matt Travi @mtravi]

@liran_tal Open to suggestions for making the details easier to find in our docs

[Matt Travi @mtravi]

@liran_tal Already supported through configuring npm directly. Our recommendation is to set in publishConfig: https://t.co/WK34iE8Isq

[npm @npmjs]

starting today, developers building npm projects on @GitHub Actions can request a provenance statement to be published alongside their package, giving consumers a verifiable way to link a package back to its source repository and build instructions.
https://t.co/8zilYJz5Dc

[Matt Travi @mtravi]

@newz2000 Are you familiar with @tidelift?

[Matt Travi @mtravi]

@MylesBorins @MarshallOfSound Makes sense. Agreed that pre-releases have by far the least risk to remove. I am hopeful that the problem can result in prioritization of solving the underlying limitation and that this allowance could then be tightened back up.

[Matt Travi @mtravi]

@MylesBorins @MarshallOfSound I've been in the fully immutable camp and would rather see the existing unpublish windows removed than more added. As a maintainer of semantic-release, I'm also in the frequent publishing camp. I'd rather wait for the existing debt to be handled than encourage more unpublishing.

[Matt Travi @mtravi]

@mando0975 Clearly a calzone https://t.co/MxMRDRJHHe