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(Snyk): Upgrade openapi-fetch from 0.9.8 to 0.10.0 #9955

Merged
merged 5 commits into from
Sep 10, 2024

Conversation

mattkrick
Copy link
Member

This PR was automatically created by Snyk using the credentials of a real user.


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade openapi-fetch from 0.9.8 to 0.10.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.

  • The recommended version was released on 21 days ago.

Release notes
Package name: openapi-fetch
  • 0.10.0 - 2024-06-20

    Minor Changes

    • ⚠️ Breaking Change: openapi-typescript@7 is needed to work. You’ll get type errors with openapi-typescript@6 and below.

    • ⚠️ Breaking Change: The Middleware API has changed to be an object rather than (request, options) or (response, options). See Middleware docs for updated API.

    • ⚠️ Breaking Change: The Content-Type header is no longer sent by default if a body payload is attached.

    • ⚠️ Breaking Change: The customFetch type now calls fetch(input: string, init: RequestInit) and the types have been updated, rather than fetch(input: Request) introduced in 0.9.0. Edit: this has been reverted due to errors reported in some environments. The 0.9.0 behavior is still present where fetch(input: Request) is called for the final request.

    • ⚠️ Breaking Change: the error type no longer is a union of all possible values; it will take the first it finds (due to some error type in some schemas being missing or incomplete, resulting in an unresolvable union)

    Patch Changes

    • Added id to middleware handlers that create a unique ID per-fetch
  • 0.9.8 - 2024-06-19

    Patch Changes

from openapi-fetch GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade openapi-fetch from 0.9.8 to 0.10.0.

See this package in npm:
openapi-fetch

See this project in Snyk:
https://app.snyk.io/org/mattkrick/project/261c96ef-7af4-4e13-a731-451e0158293e?utm_source=github&utm_medium=referral&page=upgrade-pr
@Dschoordsch Dschoordsch changed the title [Snyk] Upgrade openapi-fetch from 0.9.8 to 0.10.0 chore(Snyk): Upgrade openapi-fetch from 0.9.8 to 0.10.0 Sep 10, 2024
@Dschoordsch Dschoordsch merged commit 06f0b0b into master Sep 10, 2024
6 of 7 checks passed
@Dschoordsch Dschoordsch deleted the snyk-upgrade-d0667cff9f4b7a0b6478b1abc9a7a7a5 branch September 10, 2024 13:26
@github-actions github-actions bot mentioned this pull request Sep 10, 2024
24 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants