Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency @types/express to v5 #609

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 26, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/express (source) ^4.17.21 -> ^5.0.0 age adoption passing confidence

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Sep 26, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @myrotvorets/clean-up-after-multer@1.1.7
npm error Found: @types/express@5.0.0
npm error node_modules/@types/express
npm error   dev @types/express@"^5.0.0" from the root project
npm error   @types/express@"*" from @types/multer@1.4.12
npm error   node_modules/@types/multer
npm error     @types/multer@"^1.4.12" from the root project
npm error     peer @types/multer@"^1.4.4" from @myrotvorets/clean-up-after-multer@1.1.7
npm error     node_modules/@myrotvorets/clean-up-after-multer
npm error       @myrotvorets/clean-up-after-multer@"^1.1.7" from the root project
npm error     1 more (express-openapi-validator)
npm error
npm error Could not resolve dependency:
npm error peer @types/express@"^4.17.8" from @myrotvorets/clean-up-after-multer@1.1.7
npm error node_modules/@myrotvorets/clean-up-after-multer
npm error   @myrotvorets/clean-up-after-multer@"^1.1.7" from the root project
npm error
npm error Conflicting peer dependency: @types/express@4.17.21
npm error node_modules/@types/express
npm error   peer @types/express@"^4.17.8" from @myrotvorets/clean-up-after-multer@1.1.7
npm error   node_modules/@myrotvorets/clean-up-after-multer
npm error     @myrotvorets/clean-up-after-multer@"^1.1.7" 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 /tmp/renovate/cache/others/npm/_logs/2024-10-19T10_10_16_515Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-10-19T10_10_16_515Z-debug-0.log

Copy link

github-actions bot commented Sep 26, 2024

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails
npm/@types/express ^5.0.0 🟢 6.9
Details
CheckScoreReason
Code-Review🟢 8Found 26/29 approved changesets -- score normalized to 8
Maintained🟢 1030 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
License🟢 9license file detected
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration
Packaging⚠️ -1packaging workflow not detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Security-Policy🟢 10security policy file detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Vulnerabilities🟢 100 existing vulnerabilities detected
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
Binary-Artifacts🟢 10no binaries found in the repo
Pinned-Dependencies🟢 8dependency not pinned by hash detected -- score normalized to 8
Fuzzing⚠️ 0project is not fuzzed

Scanned Manifest Files

package.json
  • @types/express@^5.0.0
  • @types/express@^4.17.21

@renovate renovate bot force-pushed the renovate/express-5.x branch 16 times, most recently from d473a1b to f7bf7ae Compare October 2, 2024 10:31
@renovate renovate bot force-pushed the renovate/express-5.x branch 9 times, most recently from 8fcfd79 to d73dd94 Compare October 6, 2024 22:23
@renovate renovate bot force-pushed the renovate/express-5.x branch 3 times, most recently from 6e3eef4 to ec47916 Compare October 8, 2024 06:19
@renovate renovate bot force-pushed the renovate/express-5.x branch 9 times, most recently from fd3d71a to dc53b56 Compare October 17, 2024 05:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants