Bump the connectrelated group with 4 updates

[dependabot]

Bumps the connectrelated group with 4 updates: @bufbuild/buf, @bufbuild/protobuf, @bufbuild/protoc-gen-es and @bufbuild/protoplugin.

Updates @bufbuild/buf from 1.35.1 to 1.39.0

Release notes

Sourced from @​bufbuild/buf's releases.

v1.39.0

• Fix git input handling of relative HEAD refs without branch names.
• Add includes key to module configurations in v2 buf.yaml, accepting a list of directories.
  • If includes is specified, a proto file is considered in the module only if it is in one of the directories specified.
  • If both includes and excludes keys are specified for a module, a proto file is considered part of this module if it is contained in any of the include paths and not in any of the exclude paths.
• Allow multiple module configurations in the same v2 buf.yaml to have the same directory path.

v1.38.0

• Add --http3 flag to buf curl which forces buf curl to use HTTP/3 as the transport.
• Fix issue with directory inputs for v2 workspaces where the specified directory was not itself a path to a module, but contained directories with modules, and the modules would not build.
• Stop creating empty buf.lock files when buf dep update does not find new dependencies to update and there is no existing buf.lock.
• Update buf push to push the license file or doc file (e.g. README.md, LICENSE) in the same directory as buf.yaml if a module does not have a license file or doc file in the module's directory.
• Fix constraints of --path flag for lint and breaking rules to avoid resolving all files within a module. This change can result in a performance improvement for large workspaces.

v1.37.0

• Add STABLE_PACKAGE_NO_IMPORT_UNSTABLE lint rule which disallows files from stable packages to import files from unstable packages.
• Fix plugin push failures when pushing an image built with containerd image store.

v1.36.0

• Add --list-services and --list-methods flags to buf curl, which trigger the command to list known services or methods in the RPC schema, instead of invoking an RPC method.
• Add clean as a top-level option in buf.gen.yaml, matching the buf generate --clean flag. If set to true, this will delete the directories, jar files, or zip files set to out for each plugin.
• Fix git input handling of annotated tags.
• Update buf registry login to complete the login flow in the browser by default. This allows users to login with their browser and have the token automatically provided to the CLI.
• Add buf registry organization {create, delete, info, update} commands to manage BSR organizations. Remove buf beta registry organization commands.
• Add buf registry module {create, delete, deprecate, info, undeprecate, update} commands to manage BSR modules. Remove buf beta registry repository commands.
• Add buf registry label {archive, info, list, unarchive} commands to manage BSR module labels. Remove buf beta registry label commands and buf beta registry {archive, unarchive}.
• Add buf registry commit {add-label, info, list, resolve} to manage BSR module commits. Remove buf beta registry commit commands.

Changelog

Sourced from @​bufbuild/buf's changelog.

[v1.39.0] - 2024-08-27

• Fix git input handling of relative HEAD refs without branch names.
• Add includes key to module configurations in v2 buf.yaml, accepting a list of directories.
  • If includes is specified, a proto file is considered in the module only if it is in one of the directories specified.
  • If both includes and excludes keys are specified for a module, a proto file is considered part of this module if it is contained in any of the include paths and not in any of the exclude paths.
• Allow multiple module configurations in the same v2 buf.yaml to have the same directory path.

[v1.38.0] - 2024-08-22

• Add --http3 flag to buf curl which forces buf curl to use HTTP/3 as the transport.
• Fix issue with directory inputs for v2 workspaces where the specified directory was not itself a path to a module, but contained directories with modules, and the modules would not build.
• Stop creating empty buf.lock files when buf dep update does not find new dependencies to update and there is no existing buf.lock.
• Update buf push to push the license file or doc file (e.g. README.md, LICENSE) in the same directory as buf.yaml if a module does not have a license file or doc file in the module's directory.
• Fix constraints of --path flag for lint and breaking rules to avoid resolving all files within a module. This change can result in a performance improvement for large workspaces.

[v1.37.0] - 2024-08-16

• Add STABLE_PACKAGE_NO_IMPORT_UNSTABLE lint rule which disallows files from stable packages to import files from unstable packages.
• Fix plugin push failures when pushing an image built with containerd image store.

[v1.36.0] - 2024-08-06

• Add --list-services and --list-methods flags to buf curl, which trigger the command to list known services or methods in the RPC schema, instead of invoking an RPC method.
• Add clean as a top-level option in buf.gen.yaml, matching the buf generate --clean flag. If set to true, this will delete the directories, jar files, or zip files set to out for each plugin.
• Fix git input handling of annotated tags.
• Update buf registry login to complete the login flow in the browser by default. This allows users to login with their browser and have the token automatically provided to the CLI.
• Add buf registry organization {create, delete, info, update} commands to manage BSR organizations. Remove buf beta registry organization commands.
• Add buf registry module {create, delete, deprecate, info, undeprecate, update} commands to manage BSR modules. Remove buf beta registry repository commands.
• Add buf registry label {archive, info, list, unarchive} commands to manage BSR module labels. Remove buf beta registry label commands and buf beta registry {archive, unarchive}.
• Add buf registry commit {add-label, info, list, resolve} to manage BSR module commits. Remove buf beta registry commit commands.

Commits

• 496f588 Release v1.39.0 (#3272)
• 681874a Surface module description in command outputs and errors when possible (#3271)
• ba0fdb0 Add includes to v2 buf.yaml module config and allow duplicate module paths in...
• 64e1fa5 Fix git checkout for relative HEAD refs (#3266)
• 3857019 More issue template modifications (#3270)
• f1d577e More issue template modifications (#3269)
• e22893b Modify issue templates (#3268)
• d24a14d Make issue templates even stricter (#3267)
• 35adc2b Make upgrade (#3264)
• 8063ca9 Refactor bufprint package (#3173)
• Additional commits viewable in compare view

Updates @bufbuild/protobuf from 1.10.0 to 2.0.0

Release notes

Sourced from @​bufbuild/protobuf's releases.

v2.0.0

What's new in version 2

To support Protobuf editions, we have to make breaking changes that also affect users of proto2 and proto3. This prompted us to make more extensive changes that take feedback from version 1 into account:

We no longer use classes. Instead, we generate a schema object and a type for every message. To create a new instance, to serialize, and for other concerns, we provide functions. Here is a simple example:

import { create, toBinary } from "@bufbuild/protobuf";
import { UserSchema } from "./gen/example_pb";
let user = create(UserSchema, {
firstName: "Homer",
lastName: "Simpson",
active: true,
});
const bytes = toBinary(UserSchema, user);

If you use proto3, messages are now plain objects. Files with proto2 and editions use the prototype chain to track field presence.

This approach solves several outstanding issues, such as:

• bufbuild/protobuf-es#397 Provide custom options at runtime
• bufbuild/protobuf-es#551 Generated types allow assigning wrong message type if it is a superset of the target type
• bufbuild/protobuf-es#414 Improvements for proto2 required
• bufbuild/protobuf-es#738 type-save full enum value names
• bufbuild/protobuf-es#928 Better interop with 3rd party frameworks requiring plain objects
• bufbuild/protobuf-es#508 JSON types

[!TIP]

Take a look at the upgrade guide to learn more.

[!NOTE]

Connect-ES does not support version 2 yet. We will update it shortly.

Contributors

Thanks to @​srikrsna-buf for his contributions to v2!

v2.0.0-beta.3

What's Changed

This is the third beta release for version 2. See v2.0.0-alpha.1 for an introduction. To install beta packages, run npm install @bufbuild/protobuf@beta @bufbuild/protoc-gen-es@beta.

• Add GeneratedFile.array by @​timostamm in bufbuild/protobuf-es#935
• Add DescEnum.value by @​timostamm in bufbuild/protobuf-es#927
• Rename GenDescMessage to GenMessage by @​timostamm in bufbuild/protobuf-es#925
• Improve plugin option import_extension by @​timostamm in bufbuild/protobuf-es#909

... (truncated)

Commits

• 76cbbc1 Release 2.0.0 (#950)
• 64b8e61 Switch to v2 (#948)
• 1bb6d8a Add keywords to package.json files (#912)
• 5e0b35c Add mutable registry (#899)
• See full diff in compare view

Updates @bufbuild/protoc-gen-es from 1.10.0 to 2.0.0

Release notes

Sourced from @​bufbuild/protoc-gen-es's releases.

v2.0.0

What's new in version 2

To support Protobuf editions, we have to make breaking changes that also affect users of proto2 and proto3. This prompted us to make more extensive changes that take feedback from version 1 into account:

We no longer use classes. Instead, we generate a schema object and a type for every message. To create a new instance, to serialize, and for other concerns, we provide functions. Here is a simple example:

import { create, toBinary } from "@bufbuild/protobuf";
import { UserSchema } from "./gen/example_pb";
let user = create(UserSchema, {
firstName: "Homer",
lastName: "Simpson",
active: true,
});
const bytes = toBinary(UserSchema, user);

If you use proto3, messages are now plain objects. Files with proto2 and editions use the prototype chain to track field presence.

This approach solves several outstanding issues, such as:

• bufbuild/protobuf-es#397 Provide custom options at runtime
• bufbuild/protobuf-es#551 Generated types allow assigning wrong message type if it is a superset of the target type
• bufbuild/protobuf-es#414 Improvements for proto2 required
• bufbuild/protobuf-es#738 type-save full enum value names
• bufbuild/protobuf-es#928 Better interop with 3rd party frameworks requiring plain objects
• bufbuild/protobuf-es#508 JSON types

[!TIP]

Take a look at the upgrade guide to learn more.

[!NOTE]

Connect-ES does not support version 2 yet. We will update it shortly.

Contributors

Thanks to @​srikrsna-buf for his contributions to v2!

v2.0.0-beta.3

What's Changed

This is the third beta release for version 2. See v2.0.0-alpha.1 for an introduction. To install beta packages, run npm install @bufbuild/protobuf@beta @bufbuild/protoc-gen-es@beta.

• Add GeneratedFile.array by @​timostamm in bufbuild/protobuf-es#935
• Add DescEnum.value by @​timostamm in bufbuild/protobuf-es#927
• Rename GenDescMessage to GenMessage by @​timostamm in bufbuild/protobuf-es#925
• Improve plugin option import_extension by @​timostamm in bufbuild/protobuf-es#909

... (truncated)

Commits

• 76cbbc1 Release 2.0.0 (#950)
• 64b8e61 Switch to v2 (#948)
• 1bb6d8a Add keywords to package.json files (#912)
• See full diff in compare view

Updates @bufbuild/protoplugin from 1.10.0 to 2.0.0

Release notes

Sourced from @​bufbuild/protoplugin's releases.

v2.0.0

What's new in version 2

To support Protobuf editions, we have to make breaking changes that also affect users of proto2 and proto3. This prompted us to make more extensive changes that take feedback from version 1 into account:

We no longer use classes. Instead, we generate a schema object and a type for every message. To create a new instance, to serialize, and for other concerns, we provide functions. Here is a simple example:

import { create, toBinary } from "@bufbuild/protobuf";
import { UserSchema } from "./gen/example_pb";
let user = create(UserSchema, {
firstName: "Homer",
lastName: "Simpson",
active: true,
});
const bytes = toBinary(UserSchema, user);

If you use proto3, messages are now plain objects. Files with proto2 and editions use the prototype chain to track field presence.

This approach solves several outstanding issues, such as:

• bufbuild/protobuf-es#397 Provide custom options at runtime
• bufbuild/protobuf-es#551 Generated types allow assigning wrong message type if it is a superset of the target type
• bufbuild/protobuf-es#414 Improvements for proto2 required
• bufbuild/protobuf-es#738 type-save full enum value names
• bufbuild/protobuf-es#928 Better interop with 3rd party frameworks requiring plain objects
• bufbuild/protobuf-es#508 JSON types

[!TIP]

Take a look at the upgrade guide to learn more.

[!NOTE]

Connect-ES does not support version 2 yet. We will update it shortly.

Contributors

Thanks to @​srikrsna-buf for his contributions to v2!

v2.0.0-beta.3

What's Changed

This is the third beta release for version 2. See v2.0.0-alpha.1 for an introduction. To install beta packages, run npm install @bufbuild/protobuf@beta @bufbuild/protoc-gen-es@beta.

• Add GeneratedFile.array by @​timostamm in bufbuild/protobuf-es#935
• Add DescEnum.value by @​timostamm in bufbuild/protobuf-es#927
• Rename GenDescMessage to GenMessage by @​timostamm in bufbuild/protobuf-es#925
• Improve plugin option import_extension by @​timostamm in bufbuild/protobuf-es#909

... (truncated)

Commits

• 76cbbc1 Release 2.0.0 (#950)
• 64b8e61 Switch to v2 (#948)
• 1bb6d8a Add keywords to package.json files (#912)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[smaye81]

Reverted all Protobuf-ES related upgrades to 2.0 as Connect is not yet compatible with v2.