Jetify Cloud auth and Nix cache are shut down, but 0.17.2 still ships the commands (and still bills)

Aperta
  • Qualcosa non va?
#3,016 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go
Ambito
backend, cli

Direzione di ricerca

The report points to the devbox auth and devbox cache commands, the README, 0.18.0 release notes, and the login page; it names no source files or tests. First check the removals in #2940 through #2944 and the Lix hint in #2949 to understand the existing direction. The requested outcome spans 0.17.x behavior, documentation, the login page, and billing support, with no single completion check described.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug triage
What happened?

Jetify Cloud's backends are shut down, but devbox 0.17.2 still ships the commands that need them, with no deprecation notice.

Auth is gone. cloud.jetify.com redirects to auth.jetify.com/account/login, where both options fail. "Continue with email" shows "Oh no! Failed to send email. Please try again." because the page's Stytch call to /b2b/magic_links/email/discovery/send returns 404 public_token_not_found. "Continue with Google" returns the same 404. A malformed token returns a different error (400 invalid_public_token_id), so the token is well formed and was looked up: the Stytch project simply no longer exists.

Cache is gone. api.jetify.com 307s to api.jetpack.io, which returns 503 on /v4/cache and 500 elsewhere. An invalid bearer token gets the same 500, so requests never reach an auth check. cache.jetify.com does not resolve.

Why this is a 0.17.x bug. devbox auth login and devbox cache enable are still in --help and can never succeed, with no message saying why. #2940 through #2944 removed them in 0.18.x, but nixos-26.05 pins 0.17.2, so distro users are stuck with a CLI offering a login to a deleted service. I debugged my browser, email provider and PKCE state before finding the token error.

Asks

  1. Deprecation notice in the README and 0.18.0 release notes, with the shutdown date.
  2. On 0.17.x, make devbox auth and devbox cache fail with a message naming the shutdown, like #2949's Lix hint.
  3. Take the login page offline or replace it with a static notice, rather than serving a form wired to a deleted Stytch project.

Billing. Paid subscriptions were not cancelled when the backends went dark. I am on the $5/month Solo plan, lost access in August 2026, and have been billed monthly since for a service returning 503. Terms §7.6 require cancelling via Account Settings, which is behind the dead login. Other paying users are likely in the same position and unaware.

Is anyone still reading [email protected]? I wrote there on 26 September and got no reply in four weeks, while PRs kept landing here. If that inbox is unmonitored, say so and point me at one that is. Right now the only way to cancel a paid plan is a dead login and an unanswered email.

Steps to reproduce
Command

auth

devbox.json
Devbox version

0.17.2

Nix version

nix (Lix, like Nix) 2.94.2

What system does this bug occur on?

Linux (x86-64)

Debug logs

No response

Lingua principale
Go
Stelle
12.4k
Fork
358
Merge medio
17h 12m
PR unite (30g)
31

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di jetify-com/devbox

Tutte le issue di jetify-com/devbox

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.