[Snyk-dev] Upgrade @bufbuild/connect-web from 0.10.1 to 0.13.0 #5
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
Snyk has created this PR to upgrade @bufbuild/connect-web from 0.10.1 to 0.13.0. See this package in npm: https://www.npmjs.com/package/@bufbuild/connect-web See this project in Snyk: https://app.dev.snyk.io/org/37iulianpopovici/project/d207a6d8-bfcd-4a0d-88eb-f7ecfe9a0e2f?utm_source=github&utm_medium=referral&page=upgrade-pr
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 was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade @bufbuild/connect-web from 0.10.1 to 0.13.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.
Release notes
Package name: @bufbuild/connect-web
-
0.13.0 - 2023-08-17
- Handle multiple set-cookie headers from fetch API Headers object by @ tcarnes in #746
- Update gRPC and gRPC-web user agent by @ timostamm in #770
- Avoid type modifiers on import names to support TS older than 4.5 by @ timostamm in #731
- Always throw a write error back to the request iterable by @ srikrsna-buf in #732
- Fix edge cases with
- Update the
- Propagate errors thrown by
- @ tcarnes made their first contribution in #746
-
0.12.0 - 2023-07-25
- Do not block Node.js from exiting on an idle HTTP/2 connection by @ timostamm in #716
- Avoid incorrect maintained conn state by @ mustard-mh in #712
- Assert that the HTTP/2 connection is open by @ timostamm in #687
- Fix memory leak for 'error' on session during h2 requests by @ timostamm in #726
- Update ConnectError.from to keep the cause by @ timostamm in #722
- Remove deprecated protoc-gen-connect-web plugin by @ smaye81 in #717
- @ mustard-mh made their first contribution in #712
-
0.11.0 - 2023-06-29
- #686
- #692
- #695
- @ akosyakov made their first contribution in #686
-
0.10.1 - 2023-06-21
- Handle GOAWAY frames with NO_ERROR in Node.js clients by @ timostamm in #681
from @bufbuild/connect-web GitHub release notesWhat's Changed
This release changes the User-Agent used with gRPC and gRPC-web clients. Previously, the User-Agent was
@ bufbuild/connect-web, now it isconnect-es/0.13.0. Future releases will bump the version number in the User-Agent string.Enhancements
Bugfixes
AsyncIterableprotocol by @ srikrsna-buf in #729WritableIterablebehavior by @ srikrsna-buf in #724nextto request iterables by @ srikrsna-buf in #743New Contributors
Full Changelog: v0.12.0...v0.13.0
What's Changed
Improvements and fixes to the HTTP/2 session management in Node.js
Other changes
New Contributors
Full Changelog: v0.11.0...v0.12.0
What's Changed
Disregard non-JSON error response bodies for unary requests
This release makes a change in how response bodies are parsed for Connect unary requests that result in an HTTP error. Previously, all response bodies for unary requests that returned an HTTP error status were parsed with
response.json(). However, this could lead to errors with non-JSON bodies. Now, only responses with aContent-Typeofapplication/jsonwill have the body parsed as JSON and added to the resulting Connect error.For all other errors, the resulting Connect error will show the HTTP status code as the message and the corresponding Connect error code as the code.
To reiterate, this only affects Connect protocol unary requests that end with an HTTP error status code. All other protocols and/or RPC types are unaffected.
Enhancements
New Contributors
Full Changelog: v0.10.1...v0.11.0
What's Changed
Full Changelog: v0.10.0...v0.10.1
Commit messages
Package name: @bufbuild/connect-web
ManifestPreviewcomponent akuity/kargo#738)json_nameoption to Kubernetes-type fields akuity/kargo#737)Compare
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:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs