site: revert to Vercel auto-deploy; tighten routine gate to full CI parity - #165
Merged
Conversation
…arity Generation is now throttled to 3x/day, so the batched-deploy machinery is no longer needed. Restore Vercel's default behavior (production auto-deploys on merge to main, previews per PR) by removing vercel.json and the scheduled deploy workflow. Also tighten the documented content gate from `npm run validate` to `npm run check && npm run build` (= validate + astro check + build), the exact CI job. A type error passes `validate` but fails CI's `astro check`, which is what stalled auto-merge before. With the local gate mirroring CI, a green PR squash-auto-merges unattended — no CI babysitting. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01THWkDxQzDdyiEbzyRP5NF3
blokzdev
enabled auto-merge (squash)
June 24, 2026 03:32
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
2 participants
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
Generation is now throttled to 3×/day (
22 0,8,16 * * *), so deploy volume is ~3/day — far under the Vercel free-tier cap. The batched-deploy machinery (added when the routine ran hourly) now solves a problem we no longer have.Changes
Revert to Vercel auto-deploy (previews on):
vercel.json(it only heldgit.deploymentEnabled: false) → restores Vercel defaults: production auto-deploys on merge tomain, previews build per PR..github/workflows/scheduled-deploy.yml.VERCEL_DEPLOY_HOOK_URLsecret go dormant (can be removed later).Tighten the content gate to full CI parity (so PRs auto-merge hands-off):
validate → astro check → build, but the docs told routines to run onlyvalidate+build. A type error passesvalidatebut fails CI'sastro check— which is exactly what stalled auto-merge (e.g. the earlier content: add article the-gradient-thief + artifact the-inversion-window #118 fix).CLAUDE.md+docs/ROUTINES.md: the gate is nownpm run check && npm run build, and a new "Delivery & auto-merge" note makes the flow fire-and-forget — enable squash auto-merge on a gate-green PR, then end the session; production auto-deploys on merge.Verification
npm run checkpasses locally (0 errors). Changes are config deletions + markdown only, so the build is unaffected.maintrigger a production Vercel deploy again, and PRs get preview deployments.🤖 Generated with Claude Code
Generated by Claude Code