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): bump fetch-retry from 5.0.6 to 6.0.0 in /packages/traceloop-sdk #161

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

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 18, 2024

Bumps fetch-retry from 5.0.6 to 6.0.0.

Release notes

Sourced from fetch-retry's releases.

Permissive wrapping, fix global pollution and export types

Adds permissive wrapping of the fetch function while retaining the original typing of the wrapped library. This enables us to handle that there are slight variations between fetch implementations in node.

This change also removes the need for the triple-slash directive which polluted the global namespace with DOM typings. The new version also exports all the types defined in the library for good measure.

Many thanks to @​alecmev for providing an excellent PR which made these changes possible.

Commits

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Copy link
Contributor Author

dependabot bot commented on behalf of github Mar 18, 2024

The following labels could not be found: traceloop-sdk.

@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/packages/traceloop-sdk/fetch-retry-6.0.0 branch 3 times, most recently from f544211 to f80f405 Compare April 2, 2024 10:25
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/packages/traceloop-sdk/fetch-retry-6.0.0 branch 3 times, most recently from 6d54bea to e47e12a Compare April 5, 2024 11:02
Bumps [fetch-retry](https://github.com/jonbern/fetch-retry) from 5.0.6 to 6.0.0.
- [Release notes](https://github.com/jonbern/fetch-retry/releases)
- [Commits](jonbern/fetch-retry@5.0.6...6.0.0)

---
updated-dependencies:
- dependency-name: fetch-retry
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/packages/traceloop-sdk/fetch-retry-6.0.0 branch from e47e12a to 5f07795 Compare April 5, 2024 11:44
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.

None yet

0 participants