-
Notifications
You must be signed in to change notification settings - Fork 238
[comp] Production Deploy #1912
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[comp] Production Deploy #1912
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
PR SummaryUpdates buildspec to detect and package either dist/apps/api/src or dist/src outputs, ensuring main.js is found and copied correctly.
Written by Cursor Bugbot for commit 89188e4. This will update automatically on new commits. Configure here. |
|
|
Graphite Automations"Auto-assign PRs to Author" took an action on this PR • (12/12/25)1 reviewer was added to this PR based on Mariano Fuentes's automation. |
| else | ||
| echo "Using standard output structure..." | ||
| cp -r dist/* ../docker-build/ | ||
| fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: File vs directory check mismatch causes wrong copy path
The validation on line 54 checks for file existence using [ -f "dist/apps/api/src/main.js" ] with OR logic, while the copy decision on line 59 checks for directory existence using [ -d "dist/apps/api/src" ]. If the directory exists but is empty or lacks main.js, while dist/src/main.js exists in the standard location, validation passes but the copy selects the wrong source path. The directory check at line 59 needs to match the file-based check logic, such as [ -f "dist/apps/api/src/main.js" ].
Additional Locations (1)
|
🎉 This PR is included in version 1.71.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This is an automated pull request to release the candidate branch into production, which will trigger a deployment.
It was created by the [Production PR] action.