Skip to content

fix: use legacy peer dependencies to resolve installation failures#57

Merged
DariuszPorowski merged 1 commit intoraven-actions:mainfrom
jessehouwing:fix/peer-deps
Mar 2, 2026
Merged

fix: use legacy peer dependencies to resolve installation failures#57
DariuszPorowski merged 1 commit intoraven-actions:mainfrom
jessehouwing:fix/peer-deps

Conversation

@jessehouwing
Copy link
Copy Markdown
Contributor

@jessehouwing jessehouwing commented Feb 23, 2026

💌 Description

Update the npm install command to include the --legacy-peer-deps flag to resolve dependency installation failures.

Currently the action is throwing:

Cache not found for input keys: actionlint-1.7.11-Linux-X64
Run npm install --no-save --ignore-scripts @actions/[email protected]
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.9.1" from @typescript-eslint/[email protected]
npm error     node_modules/@typescript-eslint/utils
npm error       @typescript-eslint/utils@"8.56.0" from @typescript-eslint/[email protected]
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         peerOptional @typescript-eslint/eslint-plugin@"^8.0.0" from [email protected]
npm error         node_modules/eslint-plugin-jest
npm error         1 more (typescript-eslint)
npm error       3 more (@typescript-eslint/type-utils, eslint-plugin-jest, typescript-eslint)
npm error     @eslint-community/eslint-utils@"^4.8.0" from [email protected]
npm error     1 more (eslint)
npm error   peerOptional eslint@"^8.40 || 9 || 10" from @eslint/[email protected]
npm error   node_modules/@eslint/compat
npm error     dev @eslint/compat@"^2.0.2" from the root project
npm error   12 more (@eslint/js, @typescript-eslint/eslint-plugin, ...)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8 || ^9" from [email protected]
npm error node_modules/eslint-plugin-import
npm error   peerOptional eslint-plugin-import@"*" from [email protected]
npm error   node_modules/eslint-import-resolver-typescript
npm error     dev eslint-import-resolver-typescript@"^4.4.4" from the root project
npm error   dev eslint-plugin-import@"^2.32.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8 || ^9" from [email protected]
npm error   node_modules/eslint-plugin-import
npm error     peerOptional eslint-plugin-import@"*" from [email protected]
npm error     node_modules/eslint-import-resolver-typescript
npm error       dev eslint-import-resolver-typescript@"^4.4.4" from the root project
npm error     dev eslint-plugin-import@"^2.32.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /home/runner/.npm/_logs/2026-02-22T23_48_58_065Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-02-22T23_48_58_065Z-debug-0.log
Error: Process completed with exit code 1.

🔗 Related issue

Fixes: #

📚 Type of change

  • 📝 Examples / docs / tutorials
  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • 🥂 Improvement (non-breaking change which improves an existing feature)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to change)
  • 🚨 Security fix
  • ⬆️ Dependencies update

✔️ Checklist

@jessehouwing jessehouwing requested a review from a team as a code owner February 23, 2026 10:43
@DariuszPorowski DariuszPorowski changed the title Use legacy peer dependencies to resolve installation failures fix: use legacy peer dependencies to resolve installation failures Mar 2, 2026
@DariuszPorowski DariuszPorowski merged commit 59a0772 into raven-actions:main Mar 2, 2026
4 of 5 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.

2 participants