feat(ci): implement blue-green deployment strategy with canary and ro… #104
Annotations
2 errors and 5 warnings
|
Lint
Process completed with exit code 1.
|
|
Lint
frontend#lint: command (/home/runner/work/stellar-pay/stellar-pay/apps/frontend) /home/runner/setup-pnpm/node_modules/.bin/pnpm run lint exited (1)
|
|
Complete job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Lint:
apps/frontend/src/app/dashboard/webhooks/page.tsx#L4
'CheckCircle2' is defined but never used
|
|
Lint:
apps/frontend/src/app/dashboard/subscriptions/page.tsx#L4
'RefreshCw' is defined but never used
|
|
Lint:
apps/frontend/src/app/components/ui/ImageWithFallback.tsx#L25
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint:
apps/frontend/src/app/components/ui/ImageWithFallback.tsx#L21
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
Loading