chore(deps): update dependency openapi-fetch to ^0.11.0 #25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![doyobot[bot]](https://avatars.githubusercontent.com/in/325555?s=60&v=4){kind=small}
doyobot
bot
force-pushed
the
renovate/openapi-fetch-0.x
branch
from
84100c2
to
819debf
Compare
doyobot
bot
changed the title
| datasource | package | from | to | | ---------- | ------------- | ----- | ------ | | npm | openapi-fetch | 0.9.1 | 0.12.0 |
renovate
bot
force-pushed
the
renovate/openapi-fetch-0.x
branch
from
819debf
to
3a0a852
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.9.0->^0.11.0Release Notes
openapi-ts/openapi-typescript (openapi-fetch)
v0.11.1Compare Source
Patch Changes
#1831
091e71aThanks @SebastienGllmt! - Add MethodResponse utility type to easily get the return type of an endpoint on a client#1833
cec023dThanks @ngraef! - Fix identification of required properties whenstrictNullChecksis disabledUpdated dependencies [
cec023d]:v0.11.0Compare Source
Minor Changes
a956d5dThanks @gzm0! - Add support forclient["/endpoint"].GET()style callsv0.10.6Compare Source
Patch Changes
#1809
f21c05bThanks @gzm0! - perf: remove unnecessaryasynckeywords (for reduced code size)#1827
ba0d595Thanks @ngraef! - Fix typing for environments without DOM libv0.10.5Compare Source
Patch Changes
7698546Thanks @thatsprettyfaroutman! - Allow FormData through defaultBodySerializerv0.10.4Compare Source
Patch Changes
bcc9222]:v0.10.3Compare Source
Patch Changes
#1717
335530cThanks @kerwanp! - Ignore configuration files in published package#1717
335530cThanks @kerwanp! - Create own client type for easier reusabilityUpdated dependencies [
335530c]:v0.10.2Compare Source
Patch Changes
aea31a8Thanks @swachter! - Fix: encode primitive path parametersv0.10.1Compare Source
Patch Changes
#1719
a8f2253Thanks @drwpow! - Remove nanoid from dependencies#1719
a8f2253Thanks @drwpow! - Fix "failed to execute fetch on Window" error#1719
a8f2253Thanks @drwpow! - Revert customFetch API back tofetch(input: Request)v0.10.0Compare Source
Minor Changes
openapi-typescript@7is needed to work. You’ll get type errors withopenapi-typescript@6and below.(request, options)or(response, options). See Middleware docs for updated API.Content-Typeheader is no longer sent by default if a body payload is attached.customFetchtype now callsfetch(input: string, init: RequestInit)and the types have been updated, rather thanfetch(input: Request)introduced in0.9.0.Added
idto middleware handlers that create a unique ID per-fetchv0.9.8Compare Source
Patch Changes
e77ce50Thanks @armandabric! - Expose original request on Middleware.onResponsev0.9.7Compare Source
Patch Changes
64cb619Thanks @jaredLunde! - Fixes issue where native properties were not excluded from custom properties in the CustomRequest classv0.9.6Compare Source
Patch Changes
4f4253aThanks @FreeAoi! - Let request object have custom propertiesv0.9.5Compare Source
Patch Changes
645f436Thanks @FreeAoi! - fix request option types don't showing optional props correctlyv0.9.4Compare Source
Patch Changes
#1597
1f7ad9dThanks @armandabric! - Allow to select the response content type#1585
4e06f86Thanks @mikestopcontinues! - Update types for path-methods object#1610
cc8073bThanks @illright! - Fix data/error discrimination when there are empty-body errors#1587
2a66a64Thanks @JE-lee! - Fix the custom fetch typev0.9.3Compare Source
Patch Changes
4c0c7fcThanks @drwpow! - Fix type errorsv0.9.2Compare Source
Patch Changes
a5a9cc7Thanks @shirish87! - Fix 'Content-Type' header being removed from requests with multipart/form-data bodyConfiguration
📅 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.
This PR has been generated by Renovate Bot.