• Home
  • Blog
  • Projects
  • Bookshelf
  • About
← Back to all status updates

Dependabot Hell

Published 📅: ....
Last modified 📝: ....
Location 📍: Boston, MA

Share this status update on BlueskySee discussion on Bluesky


I honestly don't know how folks stay on top of dependabot PRs if you maintain anything more than 5 repos!

I'm currently trying to go through a backlog of 400+ dependabot related PRs in GitHub and it's a pain, I think this is why most folks just opt to turn it off or ignore these updates until it becomes a bigger issue...


I'm probably not the only one feeling this pain either, is probably burning quite a bit of money on builds that will fail for 5+ year old projects that I stopped working on.


Tags:

micropost

Loading...

Related Posts

micropost

Tip: Secrets for Cloudflare Workers

Published: ....

Tip: GitHub Created Date Filtering

Published: ....

Link: Next.js Is Infuriating

Published: ....

Link: What the hell is going on right now?

Published: ....

Recipe: Horchata Protein Latte

Published: ....

Zombie Retros

Published: ....

Link: How I build software quickly

Published: ....

Vacation (and streaks)

Published: ....

Polish is Important

Published: ....

<Blank> Driven Development

Published: ....

All Documentation Should Be Dated

Published: ....

Adding Microposts

Published: ....

Service Monitors and Observability

Published: ....

Leveraging service monitors properly to improve service observability.

Being Unopinionated

Published: ....

It's fine for a library to express some opinions about how it should be adopted and how the overall workflow/application in which it is adopted should function. However, it's false advertising to say that it is unopinionated.

Stop Snacking

Published: ....

No I don't mean those Milano cookies you keep taking from the office snack wall either (although you should probably stop snacking on those as often as well).

No Process is Invisible Process

Published: ....

Low/no process workflow wasn't actually no process, it was only an "invisible" process. An implicit contract with everyone on the team to do that async workflow on their own time.