Announcement: Passing the torch #3121
Comments
|
Thank you so much @evocateur for your work on this paradigm-shifting, game-changing, revolutionizing work! You're truly one of the giants who's shoulders we build software on. I hope you enjoy some well-earned rest and relaxation. |
|
Thanks, @evocateur for your work pioneering monorepos in JS! We're excited to get our hands dirty, and to start working on a roadmap with the community! |
|
Exciting news! Thank you, @evocateur, for all the fantastic work on the project. It's been a massive help for the WordPress project to maintain publishing over 80 packages with independent versioning for the last few years 🎉 |
|
Glad to see this! A big thank you to you @evocateur for the work you have done over the last few years and for the transition you are making. I've been using lerna for the past four years to deploy FoalTS packages and it has always worked very well. Many thanks to you! |
|
Great news! Thanks for the hard work over the years @evocateur! Congrats to @jeffbcross and team. |
|
Thank you @evocateur and many appreciation for all the hard work put into open source maintenance ❤️ |
|
Thanks @evocateur for your hard work and commitment to OSS. I know it's hard to pass the baton, but you rightfully did it 👊 |
|
Thanks for all the hard work @evocateur! Bless you, and I hope you recover well from your burnout. |
|
Thanks for all your work over the years @evocateur! You've had a lasting impact and always done your best! @ nrwl, I'd still be happy to stay on as a contributor, even though I've not had the time to contribute actively over the past few years |
|
@evocateur Fantastic work maintaining this over the years. Can't tell you how helpful this package has been for my development workflow. Wish you all the best in the future! |
|
That is great! |
|
Thanks for all your work over the years @evocateur 🔥 |
and use Turbo for task runner. This change replaces Lerna with https://github.com/googleapis/release-please for releasing our Mux elements packages. We started using Lerna right before it was deprecated and then saved and taken over by nrwl lerna/lerna#3121 Since then we haven't updated from v4, current version is v8, to avoid breaking things. With the creation of the media-elements monorepo and the player.style monorepo we started using Release Please which turned out to be a good experience. There is no local version bump needed and manual GH action triggers etc. but keeps the good parts like use of conventional commits and a confirmation step with an auto created release PR. Canaries are still done via the publish.sh script but I'm happy to move that over to use [wet-run](https://github.com/luwes/wet-run) if y'all are on board. It will create provenance NPM versions and the canary prerelease numbers will actually increment which is broken at the moment. The SHA hash is not needed anymore because of the provenance statements https://docs.npmjs.com/generating-provenance-statements
Howdy folks! I have some exciting news to share, as alluded to in the title.
First, some long-delayed closure: Effective today, I am stepping down as lead maintainer of Lerna. I will transition to an "emeritus" status, and largely end any remaining day-to-day responsibilities. I won't be able to pick up any threads dropped, and for that (among many other things), I sincerely apologize.
Burnout is real, friends, so I'll keep this brief.
I want to thank all past contributors to Lerna for helping make it what it is today. I am so grateful to the Lerna community for trusting me; for your patience and understanding. Maintaining Lerna has been one of the most challenging, far-reaching, and rewarding experienc 8000 es of my career. I couldn't have done it without all of you.
So, here's the announcement, effective immediately:
Nrwl is taking over stewardship of Lerna
One of my recurring nightmares, when considering who to pass the burden of maintenance onto, was that I chose wrong, enabling some nefarious scoundrel to inject a bitcoin miner (or some other disastrous toolchain attack) into Lerna. We've had enough examples over the years of well-meaning, smart folks making one tiny mistake and causing lots of pain in the package ecosystem.
However! I am truly excited that Nrwl has stepped up to take ownership of Lerna's future. Nrwl, for those that don't know, is the company behind nx, a tool I've already recommended to many folks looking for a Lerna replacement. They really get monorepos, y'know? They're also committed to healthy open source, which is extremely important to me.
One of the biggest arguments in favor of Nrwl stewarding future Lerna development, in my mind, is that they represent corporate sponsorship from a company well-aligned with the goals of Lerna itself and the community of multi-package monorepo enthusiasts. Because so much of Lerna 3 was effectively subsidized by my former employer, I believe this bodes well for the health of the project.
I will leave further details (spoiler: a roadmap!) to be announced by @nrwl folks (@jeffbcross et al), just wanted to get the message out.
The text was updated successfully, but these errors were encountered: