Repository navigation
ci(sanity): deploy Studio and functions via Blueprints in CI/CD - #698
Merged
Merged
Conversation
- Add defineStudio resource to sanity.blueprint.ts for declarative Studio deployment - Configure deployment.appId in sanity.cli.ts for automated non-interactive deployment - Update deploy.yml to deploy Studio and functions via Blueprints without swallowing errors - Add stack promotion for organization-scoped scheduled functions in CI/CD
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
⚡ Cloudflare Worker Preview Ready!
|
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.
Summary
defineStudiotoapps/sanity/sanity.blueprint.tsso the Sanity Studio is managed and deployed declaratively via Blueprints.deployment.appIdinapps/sanity/sanity.cli.tsmatching dev and production application IDs to prevent interactive prompts during automated deploys..github/workflows/deploy.ymlwith a single visibleDeploy Sanity via Blueprints (Studio & Functions)step.sanity blueprints promote --force) so organization-level scheduled functions deploy cleanly.