Repository navigation
[ENG-4594] Stop telling hosted builders to add an API key before publishing - #507
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
|
🎯 Elite quality (93%) — Consistently removes API-key requirement for hosted builders, with a clean BUILDER_PUBLISH map driving go-live behavior. 📦 Medium 🤖 Written by Claude Code — going by its own attribution. Unknown whether a person read it; agents can report that with the 🔴 High risk — changes ✅ Reviewed — approved by @daniloradovic. |
Contributor
Author
|
/review |
daniloradovic
approved these changes
Nov 20, 2026
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes ENG-4594
What changed
Connect no longer tells anyone in a hosted builder to add an API key, and no longer presents the key as required anywhere.
go-livein Replit and Bolt is now one step, the builder's own publish button, with "There is no key to add." Lovable already worked this way.go-liveknows, found from the project's.boltdirectory or named with--host bolt.go-livewith no host found no longer ends on "Add PATCHSTACK_API_KEY to its environment variables". It says to deploy as usual, and that adding the key on a self-managed host is optional.go-liveneeds.patchstackrc.local.jsononly when its steps read the key from it. A builder's workspace may not keep that file, and its steps never use it.AGENT-INSTALL.mdsays outright never to ask the person for an API key or a token, and why none is needed to publish.Why
A published app carries a read-only credential in its guard's rules file, which is enough to fetch protection rules. The full key is optional. But the CLI's own output still told people to add it:
go-livesaid "open Secrets and add PATCHSTACK_API_KEY".An assistant relays those lines, so the builder stopped and asked the person for a key they have never been shown. The package's own agent guide already said not to.
Verified
tests/go-live.test.ts: Lovable, Replit and Bolt print noPATCHSTACK_API_KEY, "Secrets" or "environment variables";.boltis detected; the key file is required only for hosts whose steps read it.go-livewith a.boltdirectory,--host replit, no host, and--host vercel(which still asks for setup first).npm run typecheck,npm run buildandcapabilities:checkare green. Fullnpm test: 4756 passed, 7 skipped.Outstanding
AGENT-INSTALL.mdand the checklist's next-step text ship in the tarball, so they cannot be field-tested before release. The hostile run is owed right after the release that carries this.Not changed
Hosted-builder detection for the environment label and for the missing-key messages still knows Lovable and Replit only. Adding Bolt there would also change how its builds are labelled, which needs its own check.
🤖 Generated with Claude Code