Repository navigation
ci: deploy the site to production from the release job, not on every push to main - #62
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Deployment failed for project stackmap-site with the following error: Learn More: https://vercel.com/docs/concepts/projects/project-configuration |
…'s 256-character limit
Contributor
|
🎉 This PR is included in version 0.6.1-rc.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Merged
Contributor
|
🎉 This PR is included in version 0.6.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
What and why
Every stable release puts two commits on
maina few minutes apart: the staging merge (old version) and the bot'schore(release): x.y.zcommit. Vercel deployed both to production, and whichever finished last went live. On 2026-10-21 the 0.5.0 merge commit landed after the 0.6.0 release commit, so the site showed 0.5.0 while npmlatestwas 0.6.0.site/vercel.json:git.deploymentEnabled.main = false, so Vercel no longer deploysmainon push. PRs andstagingstill get previews.ci.yml: a newdeploy-sitejob runs afterreleaseonmainand calls a Vercel Deploy Hook, which buildsmain's tip. An older commit can no longer replace a newer one.releasenow also needs thesitejob, so a red site build blocks the release and the deploy.../skill, since the site rendersskill/examples/. That pushedignoreCommandpast vercel.json's 256-character limit, so the check moved tosite/scripts/ignore-build.sh(same logic).Before merging into
main: create a Vercel Deploy Hook for branchmain(Project → Settings → Git → Deploy Hooks) and save its URL as the repository secretVERCEL_DEPLOY_HOOK_MAIN. Without the secret,deploy-sitefails on purpose rather than silently skipping production.How it was checked
actionlintpasses on the workflow, and the YAML and JSON both parse.ignoreCommanddry runs: with the previous SHA 3 commits back it exits 1 (build); with the previous SHA at HEAD it exits 0 (skip).main:deploy siteshould be green, Vercel should show one production deployment from the hook formain's tip, and the footer should matchnpm view @omsimos/stackmap dist-tags.latest.