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

[Snyk] Upgrade @bufbuild/connect from 0.9.1 to 0.10.0 #38

Closed

Conversation

generall
Copy link
Member

@generall generall commented Jul 5, 2023

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


Snyk has created this PR to upgrade @bufbuild/connect from 0.9.1 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 21 days ago, on 2023-06-14.
Release notes
Package name: @bufbuild/connect
  • 0.10.0 - 2023-06-14

    What's Changed

    KeepAlive

    As of this release, Connect-ES offers Basic Keepalive support for HTTP/2 for clients that use one of the transports from @ bufbuild/connect-node. Note that this replaces the option keepSessionAlive, which is deprecated with this PR.

    In it's most simple form, the following example enables regular PINGs every 5 minutes:

    https://demo.connect.build",
    pingIntervalMs: 1000 * 60 * 5,
    });">
    import { createConnectTransport } from "@ bufbuild/connect-node";

    const transport = createConnectTransport({
    httpVersion: "2",
    baseUrl: "https://demo.connect.build",
    pingIntervalMs: 1000 60 5,
    });

    For more information, see #673

    JSON parser ignores unknown fields by default

    This release also changes the default behavior of the JSON parser so that unknown fields are ignored rather than rejected. Previously, Connect-ES followed the official guidance of the proto3 language spec and rejected unknown fields by default in parsing. However, this contradicts with the ethos that adding fields to a Protobuf definition should not be a breaking change. Therefore, the default behavior has been changed so any new/unknown fields are simply ignored.

    Note that this could be considered a breaking change if consumers were relying on this rejection behavior.

    Enhancements

    • Manage HTTP/2 connections and keep them alive with PING frames by @ timostamm in #673
    • Ignore unknown JSON fields by default by @ timostamm in #642
    • Modify parsing of response for Connect unary requests by @ smaye81 in #668

    Full Changelog: v0.9.1...v0.10.0

  • 0.9.1 - 2023-05-30

    What's Changed

    Full Changelog: v0.9.0...v0.9.1

from @bufbuild/connect GitHub release notes
Commit messages
Package name: @bufbuild/connect
  • a79fcc2 Release 0.10.0
  • db0953d Pin TypeScript to 5.0.3 (#675)
  • 4c67955 Ignore unknown JSON fields in Connect unary responses (#674)
  • 5c89ecd Manage HTTP/2 connections and keep them alive with PING frames (#673)
  • 134772a Ignore unknown JSON fields by default (#642)
  • 8b62b78 Fix spelling in JSDoc and error messages (#671)
  • ce8a117 Bump jasmine from 4.6.0 to 5.0.0 (#661)
  • f19a17d Bump bufbuild/buf-setup-action from 1.17.0 to 1.20.0 (#660)
  • 61a43ae Modify parsing of response for Connect unary requests (#668)
  • 6fdde58 Update to Protobuf-ES 1.2.1 (#666)
  • f83fe73 Add more tests for Node.js universal handlers (#657)
  • a57540c Release 0.9.1 (#659)

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

@changeset-bot
Copy link

changeset-bot bot commented Jul 5, 2023

⚠️ No Changeset found

Latest commit: 7f3bad0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@IvanPleshkov IvanPleshkov changed the base branch from master to V1.7.0_with_updated_deps December 6, 2023 20:43
@IvanPleshkov IvanPleshkov changed the base branch from V1.7.0_with_updated_deps to master December 6, 2023 20:45
@IvanPleshkov IvanPleshkov changed the base branch from master to V1.7.0_with_updated_deps December 6, 2023 20:45
Base automatically changed from V1.7.0_with_updated_deps to V1.7.0 December 6, 2023 20:53
@IvanPleshkov
Copy link
Contributor

Updated here #56

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.

3 participants