Skip to content

fix: Update deploy workflow to use yarn instead of npm The repository… - #519

Open
Tboy123-emm wants to merge 1 commit into
PromptMintLabs:mainfrom
Tboy123-emm:fix/deploy-workflow-yarn-config
Open

fix: Update deploy workflow to use yarn instead of npm The repository…#519
Tboy123-emm wants to merge 1 commit into
PromptMintLabs:mainfrom
Tboy123-emm:fix/deploy-workflow-yarn-config

Conversation

@Tboy123-emm

Copy link
Copy Markdown

closes #385

… is configured for yarn (yarn.lock, .yarnrc.yml) but the deploy workflow was using npm ci which requires package-lock.json and was failing during the frontend build phase. Changes: - Switch from npm ci to yarn install --immutable in deploy-frontend job - Update cache from npm to yarn - Add corepack enable step for Node 18 compatibility - Update generate-sbom job to use yarn consistently This fixes the build failure on commit 42362f3 where npm ci was failing with 'npm ci requires existing package-lock.json' Fixes: PromptMintLabs#385 (automated rollback incident) Related to: PromptMintLabs#236 (automated rollback feature)
@drips-wave

drips-wave Bot commented Aug 28, 2026

Copy link
Copy Markdown

@Tboy123-emm Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[SEV-1] Automated rollback: Deploy - Frontend to Vercel and Artifacts failure (42362f3)

1 participant