Repository navigation
fix(deploy): re-enable platform deployments from main - #234
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Vercel Git deployments were paused in #163, so merging #232 did not deploy the platform.
Restore the previous main-only Git deployment configuration for captor-platform. Pushes to main can trigger production builds again; all existing build settings are retained.
Validation: JSON parsing and exact main/wildcard values pass; git diff --check passes. Configuration-only change.
Database reseed/schema rollout is still pending because the Neon endpoint is unreachable from the work environment. This change enables deployment; it does not claim the PR #232 database-backed routes are verified.
Closes #233.