Repository navigation
Conversation
Every main run since 6 October 2026 has failed in "publish db to supabase storage" with curl exit 6: the storage host in SUPABASE_SCORECARD_URL no longer resolves. Both secrets are unchanged since 20 August and the last upload that worked was 28 September, so the target itself went away. The tests and the build pass on those runs, but main shows red, which hides whether main is otherwise green. Nothing in this repository reads the published copy, and the built database is already attached to each run as an artifact. A failed upload now emits a warning annotation and a job-summary line and exits 0; a working upload and the no-secrets skip are unchanged. curl stays silent so the host name in the secret URL is never printed. Restoring or retiring the publish target is a separate decision. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
1 participant
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.
What
The
publish db to supabase storagejob has failed on every main run since 6 October 2026 with curl exit 6 (host not resolved). This makes a failed upload a visible warning (annotation plus job-summary line) and lets the run pass.Evidence
pytest · ruff formatandtypecheck · buildpass).gh secret listshowsSUPABASE_SCORECARD_URLandSUPABASE_SCORECARD_KEYunchanged since 2026-08-20, and the job does not take its "secrets not set" skip, so the URL is set and its host no longer resolves.mainreads the published copy (git grepforsupabase,scorecard-artifacts,latest.db.gzfinds only this job andscorecard_db/README.md). Each run still attaches the built database as an artifact.Behaviour
::warning, job-summary line, exit 0I ran the step's script locally in all three cases (an unresolvable host, empty secrets, a local HTTP server); it is shellcheck-clean. curl stays silent so the host name in the secret URL is never printed.
Not in this PR
Restoring the Supabase project or secret, or retiring the publish, needs someone with access to the Supabase account (queued for Max).
axiom: n/a: CI infrastructure.
🤖 Generated with Claude Code