Repository navigation
Run the production canary after debate-navigator deploys - #153
Merged
Merged
Conversation
Since 2026-10-16, Vercel has named its GitHub deployment environments
after the project ("Production – debate-navigator"). The canary only
matched "Production", so every post-deploy run since then was skipped.
That's 37 skipped runs, and no production deploy has been canaried since.
Match the live site's environment and keep the old name. The
debatelab-staging project's production deploys still don't start it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing: 2
Note 🎁 Summarized by CodeRabbit Free
Comment |
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
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.
Why
The production canary hasn't run after a production deploy since 2026-10-16.
prod-canary.ymlstarts only when a deployment's environment is exactlyProduction, but since 2026-10-16 Vercel has named its GitHub deployment environments after the project:Production – debate-navigator(the live site, debate.pi-stack.org)Production – debatelab-stagingPreview – debate-navigatorPreview – debatelab-stagingAll 37 recent
deployment_statusruns were skipped, including the one for #152's merge.Change
Production – debate-navigatordeployment, and still accepts plainProduction. The staging project's production deploys still don't start it.docs/testing.mdnames the environment.Checked
actionlintpasses on the workflow.if:against every environment name in this repo's deployment history. OnlyProduction – debate-navigatorandProductionmatch. The en dash matches GitHub's string byte for byte./app, every browser-facing Edge Function passes preflight, and the AI function rejects unauthenticated calls. The three signed-in tests need the Actions-only secrets and were skipped.npm run docs:checkpasses.Actions is currently refusing every job on billing grounds, so after merge this canary will start and then be refused rather than skipped. A refused job still shows that the condition matches. A full canary pass needs Actions billing fixed.
🤖 Generated with Claude Code