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

Update dependency node-fetch to v2.7.0 #11642

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 20, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
node-fetch 2.6.12 -> 2.7.0 age adoption passing confidence

Release Notes

node-fetch/node-fetch (node-fetch)

v2.7.0

Compare Source

Features

v2.6.13

Compare Source

Bug Fixes

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/node-fetch-2.x branch 6 times, most recently from 07818f6 to a1fcbb1 Compare May 21, 2024 12:01
Copy link
Contributor

@karinathomasbbc karinathomasbbc left a comment

Choose a reason for hiding this comment

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

Requires testing on preview environment for Opera Mini

@renovate renovate bot force-pushed the renovate/node-fetch-2.x branch 7 times, most recently from 0bb75fe to cd08134 Compare May 22, 2024 14:12
@karinathomasbbc
Copy link
Contributor

Requires testing on preview environment for Opera Mini

Or does it? @amoore108 are we OK to update node fetch (like undici), or do we need to do some manual testing first?

@renovate renovate bot force-pushed the renovate/node-fetch-2.x branch 13 times, most recently from eada456 to ef68649 Compare May 29, 2024 13:29
@renovate renovate bot force-pushed the renovate/node-fetch-2.x branch from ef68649 to 919102c Compare May 31, 2024 12:53
@renovate renovate bot force-pushed the renovate/node-fetch-2.x branch 2 times, most recently from c51620f to dc89cc6 Compare June 3, 2024 09:59
Copy link
Contributor Author

renovate bot commented Jun 4, 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.json
Post-upgrade command 'yarn install' has not been added to the allowed list in allowedPostUpgradeCommands

@renovate renovate bot force-pushed the renovate/node-fetch-2.x branch 3 times, most recently from e559383 to c558d0d Compare June 4, 2024 10:55
@renovate renovate bot force-pushed the renovate/node-fetch-2.x branch from c558d0d to bcda3db Compare June 4, 2024 14:08
@amoore108
Copy link
Contributor

Closing out to let Dependabot pick this up

@amoore108 amoore108 closed this Jul 19, 2024
@renovate renovate bot deleted the renovate/node-fetch-2.x branch July 21, 2024 08:42
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