search

dashpay / tenderdash

⟁ Tenderdash Core (SBFT Consensus) in Go
https://www.dashpay.org
Other
18 stars 14 forks source link

build(deps): Bump github.com/bufbuild/buf from 1.35.1 to 1.42.0 #928

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps github.com/bufbuild/buf from 1.35.1 to 1.42.0.

Release notes

Sourced from github.com/bufbuild/buf's releases.

v1.42.0

  • Add support for custom lint and breaking change plugins. See our launch blog post for more details!
  • Add buf dep graph --format flag that defaults to dot, and adds the option json, to print the dependency graph in JSON format.
  • Fix bugs in buf format where trailing comments on commas in message literals were not properly propagated to the formatted proto, empty message literals were not properly indented, and compound strings in options added an extra newline before trailing commas.

v1.41.0

  • Add HTTP/3 support for gRPC with buf curl.
  • Fix issue where errors from protoc plugins may be overwritten when executing plugins in parallel.

v1.40.1

  • Fix issue with buf lint where comment ignores in the shape of // buf:lint:ignore <RULE_ID> <extra comment> were not recognized due to the extra comment.

v1.40.0

  • Add concept of a default lint or breaking rule, which is printed out as a property when running buf config ls-{breaking,lint}-rules. Default rules are those rules which are run if no lint or breaking rules are explicitly configured in your buf.yaml.
  • Rename DEFAULT lint rule category to STANDARD. With the concept of default rules being introduced, having a category named DEFAULT is confusing, as while it happens that all the rules in the DEFAULT lint category are also default rules, the name has become overloaded. As with all buf changes, this change is backwards-compatible: the DEFAULT lint category continues to work, and always will. We recommend changing to STANDARD, however.

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.

... (truncated)

Changelog

Sourced from github.com/bufbuild/buf's changelog.

[v1.42.0] - 2024-09-18

  • Add support for custom lint and breaking change plugins. See our launch blog post for more details!
  • Add buf dep graph --format flag that defaults to dot, and adds the option json, to print the dependency graph in JSON format.
  • Fix bugs in buf format where trailing comments on commas in message literals were not properly propagated to the formatted proto, empty message literals were not properly indented, and compound strings in options added an extra newline before trailing commas.

[v1.41.0] - 2024-09-11

  • Add HTTP/3 support for gRPC with buf curl.
  • Fix issue where errors from protoc plugins may be overwritten when executing plugins in parallel.

[v1.40.1] - 2024-09-06

  • Fix issue with buf lint where comment ignores in the shape of // buf:lint:ignore <RULE_ID> <extra comment> were not recognized due to the extra comment.

[v1.40.0] - 2024-09-04

  • Add concept of a default lint or breaking rule, which is printed out as a property when running buf config ls-{breaking,lint}-rules. Default rules are those rules which are run if no lint or breaking rules are explicitly configured in your buf.yaml.
  • Rename DEFAULT lint rule category to STANDARD. With the concept of default rules being introduced, having a category named DEFAULT is confusing, as while it happens that all the rules in the DEFAULT lint category are also default rules, the name has become overloaded. As with all buf changes, this change is backwards-compatible: the DEFAULT lint category continues to work, and always will. We recommend changing to STANDARD, however.

[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.

... (truncated)

Commits
  • 5244a82 Release v1.42.0 (#3330)
  • 82e9594 Enable plugins by default remove BUF_BETA_PLUGINS_ENABLED (#3326)
  • 43df40a Add --format=json to buf dep graph (#3320)
  • 411778b Update bufcheck.RunnerProvider to use PluginConfig (#3328)
  • 4e2a48f Fix comments on separators and handling message literals and compound strings...
  • d688c1f Remove v1alpha1 Labels and Sync Services (#3329)
  • 26ce1b0 Make upgrade (#3324)
  • 6df73b9 Adjust end line and column expectations in lint and breaking tests (#3319)
  • e8e776e Use pre-release tag for protoreflect/v2 instead of commit-hash pseudo-tag (#3...
  • 72a0a4b Update bufimageutil test to protoprint v2 (#3314)
  • Additional commits viewable in compare view


Dependabot compatibility score

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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
github-actions[bot] commented 1 month ago

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

coderabbitai[bot] commented 1 month ago

[!IMPORTANT]

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
dependabot[bot] commented 1 month ago

Superseded by #946.