Open lamontadams opened 1 month ago
Hello @lamontadams Thank you for creating this issue. We will investigate it and get back to you as soon as we have some feedback.
Hello @lamontadams, Thank you once again for creating this issue, we have tried to reproduce the issue but the workflow run is successful within few seconds without any hang and we are unable to see the warning for Node.js versions 21 and 18 for v4. Please find the below screenshots for reference. The warning messages indicate that there is a peer dependency conflict with the react version. This is not an error but a warning that can be resolved by adjusting dependencies.
To resolve this issue, you can use --legacy-peer-deps flag with npm ci to install dependencies ignoring peer dependency conflicts:
Updated Workflow Configuration jobs: build_and_push: runs-on: ubuntu-latest environment: qa steps:
name: Checkout code uses: actions/checkout@v3
name: Set up Node.js uses: actions/setup-node@v3 with: node-version: '21' scope: '@recurate' registry-url: 'https://npm.pkg.github.com'
name: Install Dependencies and Build env: NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }} GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} NODE_ENV: qa run: | npm ci --legacy-peer-deps npm run build This should bypass the peer dependency conflict warnings and proceed with the installation and build process.
Please update us if this workaround fix your issue.
Thanks! We will give this a try and let you know what happens.
On Fri, Jul 19, 2024 at 7:57 AM aparnajyothi-y @.***> wrote:
Hello @lamontadams https://github.com/lamontadams, Thank you once again for creating this issue, we have tried to reproduce the issue but the workflow run is successful within few seconds without any hang and we are unable to see the warning for Node.js versions 21 and 18 for v4. Please find the below screenshots for reference. The warning messages indicate that there is a peer dependency conflict with the react version. This is not an error but a warning that can be resolved by adjusting dependencies.
image.png (view on web) https://github.com/user-attachments/assets/fc72a482-7b98-4aad-bd26-ea61e2fcd55d
image.png (view on web) https://github.com/user-attachments/assets/d3c62743-6884-498d-82d2-3c4fb9091cbc
image.png (view on web) https://github.com/user-attachments/assets/fb5ce977-8d82-4b67-9036-ee83dc6e60a2
To resolve this issue, you can use --legacy-peer-deps flag with npm ci to install dependencies ignoring peer dependency conflicts:
Updated Workflow Configuration jobs: build_and_push: runs-on: ubuntu-latest environment: qa steps:
name: Checkout code uses: @.***
name: Set up Node.js uses: @. with: node-version: '21' scope: @.' registry-url: 'https://npm.pkg.github.com'
name: Install Dependencies and Build env: NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }} GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} NODE_ENV: qa run: | npm ci --legacy-peer-deps npm run build
This should bypass the peer dependency conflict warnings and proceed with the installation and build process.
Please update us if this workaround fix your issue.
— Reply to this email directly, view it on GitHub https://github.com/actions/setup-node/issues/1097#issuecomment-2238985002, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJEQA6NKBTZLPHVUYTF6ADZND5LHAVCNFSM6AAAAABKCFNFP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZYHE4DKMBQGI . You are receiving this because you were mentioned.Message ID: @.***>
Hello @lamontadams, Please check and update the workaround fix the issue.
Hi there. I have heard that it does indeed work. Thank you!Sent from my iPhoneOn Jul 31, 2024, at 10:13 AM, aparnajyothi-y @.***> wrote: Hello @lamontadams, Please check and update the workaround fix the issue.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
Description: For certain versions of node,
npm ci
hangs until github kills the workflow (about 6 hours).Failing versions:
Working versions:
npm ci
runs successfully for the same package.json locally on all of the above identified failing versions.Action version: Currently 4.0.2, observed same behavior with version 3 and 2.
Platform:
Runner type:
Tools version: npm package manager, failure noted with node version 18 and 21.
Repro steps:
Workflow yaml - this uses v3 of the action but as stated above, I have seen this issue with versions 2 and 4.02 (which I understand to be the current latest):
Expected behavior: npm ci executes correctly
Actual behavior: npm ci outputs some (sadly expected) warnings and hangs until the workflow execution is terminated.