Repository navigation
chore(release): remove docs deploy job - #936
Merged
Merged
Conversation
Vercel CLI project-scoped tokens can fail its account/team auto-discovery even when the project ID is accessible. Write the explicit project link from the configured IDs before pulling deployment settings.
Stop coupling documentation availability to Vercel CLI credentials in the release pipeline. Record that the site remains manually deployed while Vercel Git deployments are disabled.
vastsa
changed the title
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.
Remove the release-triggered Vercel documentation deployment job.
The Vercel project has Git deployments disabled, so documentation will no longer publish automatically. The release runbook now states that deployments are manual when needed.
Validation: pnpm docs:check, workflow YAML parse, and git diff --check.