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

build: update pre-commit #52

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

build: update pre-commit #52

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 24, 2024

This PR contains the following updates:

Package Type Update Change
alessandrojcm/commitlint-pre-commit-hook repository minor v9.11.0 -> v9.18.0
bufbuild/buf repository minor v1.28.1 -> v1.47.2
golangci/golangci-lint repository minor v1.58.1 -> v1.62.0

Note: The pre-commit manager in Renovate is not supported by the pre-commit maintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.


Release Notes

alessandrojcm/commitlint-pre-commit-hook (alessandrojcm/commitlint-pre-commit-hook)

v9.18.0

Compare Source

Features
  • bump the commitlint group with 2 updates (1beaa58)

v9.17.0

Compare Source

Features
  • bump the commitlint group with 2 updates (ba3ef22)
  • bump the commitlint group with 2 updates (6644bfa)

v9.16.0

Compare Source

Features
  • bump the commitlint group with 2 updates (75c8c9b)

v9.15.0

Compare Source

Features
  • bump the commitlint group with 2 updates (b27b4a4)

v9.14.0

Compare Source

Features
  • bump the commitlint group with 2 updates (8f4d925)
  • bump the commitlint group with 2 updates (a5e9a14)
  • bump the commitlint group with 2 updates (a884f9a)

v9.13.0

Compare Source

Features
  • bump the commitlint group with 2 updates (61f9e97)
  • bump the commitlint group with 2 updates (28ca409)
  • converted to ESM (a203e19)

v9.12.0

Compare Source

Features
  • bump the commitlint group with 2 updates (cf4cb1e)
  • bump the commitlint group with 2 updates (076334a)
  • bump the commitlint group with 2 updates (0e51133)
  • bump the commitlint group with 2 updates (7075f07)
bufbuild/buf (bufbuild/buf)

v1.47.2

Compare Source

  • Update the patch version to resolve NPM packaging issues. No command updates or user changes.

v1.47.1

Compare Source

  • Update the patch version to resolve NPM packaging issues. No command updates or user changes.

v1.47.0

Compare Source

  • Move buf registry commit to buf registry module commit. Command
    buf registry commit is now deprecated.
  • Move buf registry label to buf registry module label. Command
    buf registry label is now deprecated.

v1.46.0

Compare Source

  • Add buf registry whoami command, which checks if you are logged in to the Buf Schema
    Registry at a given domain.

v1.45.0

Compare Source

  • Update buf registry module info --format=json to add default_label_name, which provides the name
    of the default label of a module.

v1.44.0

Compare Source

  • Update the PROTOVALIDATE lint rule to check example field options. Examples will be checked that
    they satisfy the field constraints, and are only present if constraints are present.
  • Update the PROTOVALIDATE lint rule to check predefined rules. Predefined rules will be checked
    that they compile.
  • Add support for a WebAssembly (Wasm) runtime for custom lint and breaking changes plugins. Use the
    .wasm file extension to specify a path to a Wasm plugin.

v1.43.0

Compare Source

  • Add new experimental LSP support under buf beta lsp.

v1.42.0

Compare Source

  • 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

Compare Source

  • 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

Compare Source

  • 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

Compare Source

  • 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

Compare Source

  • 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

Compare Source

  • 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

Compare Source

  • 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

Compare Source

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

v1.35.1

Compare Source

  • Fix the git input parameter ref to align with the git notion of a ref. This allows for the use
    of branch names, tag names, and commit hashes.
  • Fix unexpected buf build errors with absolute path directory inputs without workspace and/or
    module configurations (e.g. buf.yaml, buf.work.yaml) and proto file paths set to the --path flag.

v1.35.0

Compare Source

  • Add buf generate --clean flag that will delete the directories, jar files, or zip files that the
    plugins will write to, prior to generation. Allows cleaning of existing assets without having
    to call rm -rf.
  • Deprecate --username flag on and username prompt on buf registry login. A username is no longer
    required to log in.

v1.34.0

Compare Source

  • Add buf config ls-modules command to list configured modules.
  • Fix issue where buf generate would succeed on missing insertion points and
    panic on empty insertion point files.
  • Update buf generate to allow the use of Editions syntax when doing local code
    generation by proxying to a protoc binary (for languages where code gen is
    implemented inside of protoc instead of in a plugin: Java, C++, Python, etc).
  • Allow use of an array of strings for the protoc_path property of for buf.gen.yaml,
    where the first array element is the actual path and other array elements are extra
    arguments that are passed to protoc each time it is invoked.

v1.33.0

Compare Source

  • Allow user to override --source-control-url and --create-default-label when using
    --git-metadata with buf push.
  • Fix buf push --git-metadata when local tags point to different objects than
    the remote tags.
  • Fix issue where comment ignores were not respected for PROTOVALIDATE lint rule violations.
  • Add buf beta registry label {create,get,list} to replace buf beta registry {draft, tag}
    commands.
  • Update buf beta commit {get,list} command outputs to display create time and stop
    displaying associated tags.
  • Change the behavior of buf beta commit list <buf.build/owner/repository> when the
    reference is empty. It now lists commits in the repository instead of listing commits
    of the default label.
  • Update output of buf format to canonicalize the punctuation used in message literals
    in option values. The output now always uses { and } instead of < and >; it
    adds : separators between field names and message values if the source omitted them,
    and it removes unnecessary separators between fields (, and ; are allowed, but
    neither is needed).
  • Update buf format -w so that it does not touch files whose contents don't actually
    change. This eliminates noisy notifications to file-system-watcher tools that are
    watching the directory that contains proto sources.
  • Update buf generate to work with plugins provided by protoc for versions v24.0
    to v25.3. Editions support was experimental in these releases, and the plugins
    advertise incomplete support for editions, which triggers buf to report an error.
    With this fix, these plugins can be used again as long as none of the input files use
    editions syntax.
  • Add buf push --exclude-unnamed flag to exclude unnamed modules when pushing to the BSR.

v1.32.2

Compare Source

  • Update buf generate to warn instead of error when proto3 optional is required but not
    supported by a plugin.

v1.32.1

Compare Source

  • Fix archive and git inputs so that --path and --exclude-path paths are relative to
    the #subdir rather than the root of the input. This fixes an unintended behavior change
    that was introduced in v1.32.0.
  • Add module input for protoc-gen-buf-lint and protoc-gen-buf-breaking to allow
    users to specify the module for v2 configuration files.

v1.32.0

Compare Source

  • Add version v2 for buf.yaml and buf.gen.yaml configuration files.
  • Add buf config migrate to migrate configuration files to the latest version (now v2).
  • Move buf mod init to buf config init. buf mod init is now deprecated.
  • Move buf mod ls-lint-rules to buf config ls-lint-rules. buf mod ls-lint-rules is now
    deprecated.
  • Move buf mod ls-breaking-rules to buf config ls-breaking-rules. buf mod ls-breaking-rules
    is now deprecated.
  • Move buf mod prune to buf dep prune. buf mod prune is now deprecated.
  • Move buf mod update to buf dep update. buf mod update is now deprecated.
  • Move buf mod {clear-cache,cc} to buf registry cc. buf mod {clear-cache,cc} is now
    deprecated.
  • Move buf beta graph to stable as buf dep graph.
  • Change the default visibility of buf push --create-visibility to private when the --create
    flag is set. Users are no longer required to set --create-visibility when running
    buf push --create.
  • Add buf push --label, which allows users to set labels when pushing new commits to the BSR.
  • Add buf push --source-control-url, which allows users to associate commits pushed to the BSR
    with a URL to a source code repository.
  • Add buf push --create-default-label, which allows users to set a default label for a repository
    when calling buf push --create.
  • Add buf push --git-metadata, which automatically sets appropriate --label,
    --source-control-url, and --create-default-label flags based on the current Git repository.
  • Add buf convert --validate to apply protovalidate
    rules to incoming messages specified with --from.
  • Deprecate buf mod open.
  • Delete buf beta migrate-v1beta1 This is now replaced with buf config migrate.
  • Add buf registry sdk version to get the version of a Generated SDK for a module and plugin.
  • Add buf beta registry archive and buf beta registry unarchive commands for archiving and
    unarchiving labels on the BSR.
  • Add support for Protobuf Editions. This allows buf to be used with sources that use edition
    2023, instead of proto2 or proto3 syntax. This also updates the protoc-gen-buf-breaking and
    protoc-gen-buf-lint Protobuf plugins to support files that use edition 2023.
  • Update buf breaking rules to work with Protobuf Editions. To support Editions, some rules have
    been deprecated and replaced with Editions-aware rules. All deprecated rules continue to work
    for existing users.
    • FIELD_SAME_CTYPE has been replaced with FIELD_SAME_CPP_STRING_TYPE, which considers both
      ctype field options and new (pb.cpp).string_type features when deciding on backwards
      compatibility.
    • FIELD_SAME_LABEL has been replaced with three rules that all check "cardinality". The new
      rules can distinguish between maps and other repeated fields and between implicit and explicit
      field presence. The new rules are:
      1. FIELD_SAME_CARDINALITY in the FILE and PACKAGE categories.
      2. FIELD_WIRE_COMPATIBLE_CARDINALITY in the WIRE category.
      3. FIELD_WIRE_JSON_COMPATIBLE_CARDINALITY in the WIRE_JSON category.
    • FILE_SAME_JAVA_STRING_CHECK_UTF8 has been replaced with FIELD_SAME_JAVA_UTF8_VALIDATION,
      which considers both the java_string_check_utf8 file option and (pb.java).utf8_validation
      features when deciding on backwards compatibility.
    • Add to the existing FILE_SAME_SYNTAX rule with a few related rules that can catch the same
      sort of compatibility issues, but in an Editions source file that changes feature values:
      1. MESSAGE_SAME_JSON_FORMAT and ENUM_SAME_JSON_FORMAT catch changes to the json_format
        feature, which controls whether support for the JSON format is best-effort or properly
        supported. When supported, the compiler performs more checks relating to field name
        collisions for the JSON format as well as for FieldMask usage.
      2. FIELD_SAME_UTF8_VALIDATION catches changes to the utf8_validation feature, which
        controls validation of string values.
      3. ENUM_SAME_TYPE catches changes to an enum's type, open vs. closed.
  • Add support for extensions to buf breaking. All existing rules for fields are now applied to
    extensions, except for FIELD_NO_DELETE (and its variants). There are also new
    EXTENSION_NO_DELETE and PACKAGE_EXTENSION_NO_DELETE rules for catching deletions of an
    extension. The new rules are not active by default in existing v1 and v1beta1
    configurations, for backwards-compatibility reasons. Migrate your config to v2 to use them.
  • Add support for top-level extensions to buf lint. It previously only checked extensions that
    were defined inside of messages.
  • Add a new FIELD_NOT_REQUIRED lint rule that prevents use of required in proto2 files and of
    features.field_presence = LEGACY_REQUIRED in Editions files. This new rule is not active by
    default in existing v1 and v1beta1 configurations, for backwards-compatibility reasons.
    Migrate your config to v2 to use them.

v1.31.0

Compare Source

  • Update dependencies.

v1.30.1

Compare Source

  • Fix issue where buf lint incorrectly reports an error for (buf.validate.field).repeated
    is set for a repeated validation rule.

v1.30.0

Compare Source

  • Update buf generate so it populates the recently-added
    source_file_descriptors
    field of the CodeGeneratorRequest message. This provides the plugin with access to options
    that are configured to only be retained in source and not at runtime (via
    field option).
    Descriptors in the proto_file field will not include any options configured this way
    for the files named in file_to_generate field.
  • Add --exclude-source-retention-options flag to buf build, which
    causes options configured to only be retained in source to be stripped
    from the output descriptors.

v1.29.0

Compare Source

  • Add support for yaml format. All commands that take image inputs, output images,
    or convert between message formats, now take yaml as a format, in addition to
    the existing binpb and txtpb formats. Some examples:
    • buf build -o image.yaml
    • buf ls-files image.yaml
    • buf convert --type foo.Bar --from input.binpb --to output.yaml
  • The yaml and json formats now accept two new options: use_proto_names and
    use_enum_numbers. This affects output serialization. Some examples:
    • buf convert --type foo.Bar --from input.binpb --to output.yaml#use_proto_names=true
    • buf convert --type foo.Bar --from input.binpb --to -#format=yaml,use_enum_numbers=true
  • Fix issue where buf format would inadvertently mangle files that used
    the expanded Any syntax
    in option values.
golangci/golangci-lint (golangci/golangci-lint)

v1.62.0

Compare Source

v1.61.0

Compare Source

  1. Enhancements
    • Add junit-xml-extended format
    • Exclude Swagger Codegen files by default
  2. Updated linters
    • dupword: from 0.0.14 to 0.1.1
    • fatcontext: from 0.4.0 to 0.5.2
    • gci: from 0.13.4 to 0.13.5 (new option no-lex-order)
    • go-ruleguard: from 0.4.2 to 0fe6f58 (fix panic with custom linters)
    • godot: from 1.4.16 to 1.4.17
    • gomodguard: from 1.3.3 to 1.3.5
    • gosec: disable temporarily G407
    • gosec: from ab3f6c1 to 2.21.2 (partially fix G115)
    • intrange: from 0.1.2 to 0.2.0
    • nolintlint: remove the empty line in the directive replacement
  3. Misc.
    • Improve runtime version parsing
  4. Documentation
    • Add additional info about typecheck

v1.60.3

Compare Source

v1.60.2

Compare Source

v1.60.1

Compare Source

v1.60.0

Compare Source

v1.59.1

Compare Source

  1. Updated linters
    • go-errorlint: from 1.5.1 to 1.5.2
    • gomnd: deprecated configuration compatibility
    • intrange: add style preset
    • misspell: from 0.5.1 to 0.6.0
    • sloglint: from 0.7.0 to 0.7.1
    • testifylint: from 1.3.0 to 1.3.1
    • unparam: bump to HEAD
    • usestdlibvars: from 1.25.0 to 1.26.0
  2. Fixes
    • SARIF: init empty result slice
    • SARIF: issue column >= 1
  3. Documentation
    • update revive configuration

v1.59.0

Compare Source

v1.58.2

Compare Source

  1. Updated linters
    • canonicalheader: from 1.0.6 to 1.1.1
    • gosec: from 2.19.0 to 2.20.0
    • musttag: from 0.12.1 to 0.12.2
    • nilnil: from 0.1.8 to 0.1.9
  2. Documentation
    • Improve integrations and install pages

Configuration

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title build: update pre-commit hook bufbuild/buf to v1.29.0 build: update pre-commit Feb 7, 2024
@renovate renovate bot force-pushed the renovate/pre-commit branch 2 times, most recently from a7d35a7 to eae0a7c Compare February 8, 2024 19:18
@renovate renovate bot force-pushed the renovate/pre-commit branch 2 times, most recently from abab2c0 to 60b3aa7 Compare March 1, 2024 20:08
@renovate renovate bot force-pushed the renovate/pre-commit branch 2 times, most recently from 8458fbd to cf3a9a0 Compare March 20, 2024 18:59
@renovate renovate bot force-pushed the renovate/pre-commit branch 3 times, most recently from 3ee5fe7 to 3f90f5c Compare April 3, 2024 21:46
@renovate renovate bot force-pushed the renovate/pre-commit branch 2 times, most recently from f91b299 to 6aa5bfd Compare April 23, 2024 17:36
@renovate renovate bot force-pushed the renovate/pre-commit branch 2 times, most recently from a98370d to 28bd67b Compare May 8, 2024 21:35
@renovate renovate bot force-pushed the renovate/pre-commit branch 3 times, most recently from 9e06407 to b5d3089 Compare May 21, 2024 22:37
@renovate renovate bot force-pushed the renovate/pre-commit branch 2 times, most recently from 7d3f899 to 146743a Compare May 28, 2024 19:47
@renovate renovate bot force-pushed the renovate/pre-commit branch 2 times, most recently from 800fb81 to c42d2c0 Compare June 13, 2024 18:06
@renovate renovate bot force-pushed the renovate/pre-commit branch 2 times, most recently from 22b56f3 to 9fc3d71 Compare June 28, 2024 07:39
Copy link

codecov bot commented Jul 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 54.44%. Comparing base (3cf2082) to head (5455130).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #52      +/-   ##
==========================================
- Coverage   54.81%   54.44%   -0.38%     
==========================================
  Files          25       25              
  Lines        1609     1969     +360     
==========================================
+ Hits          882     1072     +190     
- Misses        630      800     +170     
  Partials       97       97              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/pre-commit branch 3 times, most recently from c39a90c to d9231b4 Compare August 16, 2024 20:22
@renovate renovate bot force-pushed the renovate/pre-commit branch 3 times, most recently from 268a794 to e337df3 Compare August 23, 2024 01:14
@renovate renovate bot force-pushed the renovate/pre-commit branch 2 times, most recently from 2c5af84 to 3604de0 Compare August 28, 2024 17:16
@renovate renovate bot force-pushed the renovate/pre-commit branch 5 times, most recently from 8dac7f7 to eac0838 Compare September 11, 2024 19:48
@renovate renovate bot force-pushed the renovate/pre-commit branch 2 times, most recently from 317c185 to 997f32c Compare October 3, 2024 16:29
@renovate renovate bot force-pushed the renovate/pre-commit branch 3 times, most recently from 2a1d5bc to 0ac299b Compare November 14, 2024 14:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants