Dead already?

[johncmunson]

Not to be that guy, but... it's been two months and no commits.

What's up with that? I mean, there's nothing inherently wrong with that I suppose. But, it's not exactly a thing you'd expect to see from a project that is supposedly "under active development" and "marching toward v1.0".

[ossiefisheater]

I've seen various dead Google Cloud CLIs and get to wondering whether the higher-ups at Google have called a stop to it.

[malob]

First off, genuine thanks to @jpoehnelt and everyone who's contributed here. This tool has quietly become load-bearing in my day-to-day workflows, and I don't take that for granted.

I wanted to pick up @johncmunson's question in a more constructive spirit, since I think several of us would just appreciate clarity rather than an explanation we're owed. A few things I've noticed:

• The last release and merged PR were both 2026-03-31, about ten weeks ago.
• Open PRs have been steadily piling up (there's a whole batch of community fixes sitting unreviewed), and even the project's own automated PRs (the release-versions and "sync skills with Discovery API" bot PRs) are now unmerged.
• The stale bot is still running unattended, and that has a real cost: it auto-closes reviewed, passing contributor PRs after 72 hours (see Stale PRs and Automatic Closure #763). Since only maintainers can reopen, those contributions effectively evaporate. A few of my own fixes went this way.

And this isn't just about new features. Several of the unmerged PRs (including a few of mine) fix actual bugs in shipped functionality, where both the bug and the fix are already known. I'm only getting by because I run a fork with those patches applied; anyone on the released version is stuck with the bugs and no path forward.

None of this is a complaint. Priorities shift, people get busy, and this is explicitly "not an officially supported Google product," so nobody's entitled to anything here. But the uncertainty makes it hard to plan: contributors don't know whether it's worth opening PRs, and users don't know whether to keep depending on the tool.

So mostly: @jpoehnelt, when you have a moment, could you share where things stand? Even "paused indefinitely," "blocked on internal stuff," or "actively looking for help" would be genuinely useful. Any of those lets people make good decisions. And if there's a lightweight way for contributors to help keep the lights on (triage, reviews, or even just pausing the stale bot so reviewed PRs stop disappearing), I'd be glad to pitch in where I can.

Thanks again for building this.

[johncmunson]

far too much entitlement going on in this thread. best to close it down.