Skip to content

Update workflows to use --legacy-peer-deps#226

Merged
dcsturman merged 2 commits intocanaryfrom
dev-security-patch
Dec 19, 2025
Merged

Update workflows to use --legacy-peer-deps#226
dcsturman merged 2 commits intocanaryfrom
dev-security-patch

Conversation

@dcsturman
Copy link
Owner

No description provided.

@augmentcode
Copy link

augmentcode bot commented Dec 19, 2025

🤖 Augment PR Summary

Summary: Updates the frontend deploy GitHub Actions workflows to install dependencies using legacy peer-dependency resolution.

Changes:

  • Added --legacy-peer-deps to npm ci in the canary and production FE build/deploy workflows

Why: Helps CI builds proceed when strict peer dependency resolution causes npm ci to fail on the runner.

🤖 Was this summary useful? React with 👍 or 👎

Copy link

@augmentcode augmentcode bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review completed. 1 suggestions posted.

Fix All in Augment

Comment augment review to trigger a new review at any time.

VITE_GOOGLE_OAUTH_CLIENT_ID: ${{ env.GOOGLE_CLIENT_ID }}
working-directory: ./fe/callisto
run: npm ci && npm run build
run: npm ci --legacy-peer-deps && npm run build
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

npm ci --legacy-peer-deps depends on npm v7+ behavior; since these workflows don’t pin Node/npm, consider setting an explicit Node version to reduce the risk of future runner image changes breaking installs (also applies to the prod workflow).

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎

@dcsturman dcsturman merged commit 477c9a9 into canary Dec 19, 2025
6 checks passed
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.

1 participant