-
Notifications
You must be signed in to change notification settings - Fork 0
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
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/pre-commit
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
renovate
bot
changed the title
build: update pre-commit hook bufbuild/buf to v1.29.0
build: update pre-commit
Feb 7, 2024
renovate
bot
force-pushed
the
renovate/pre-commit
branch
2 times, most recently
from
February 8, 2024 19:18
a7d35a7
to
eae0a7c
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
from
February 15, 2024 18:57
eae0a7c
to
af24c6b
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
2 times, most recently
from
March 1, 2024 20:08
abab2c0
to
60b3aa7
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
from
March 8, 2024 00:56
60b3aa7
to
6769686
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
2 times, most recently
from
March 20, 2024 18:59
8458fbd
to
cf3a9a0
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
3 times, most recently
from
April 3, 2024 21:46
3ee5fe7
to
3f90f5c
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
2 times, most recently
from
April 23, 2024 17:36
f91b299
to
6aa5bfd
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
2 times, most recently
from
May 8, 2024 21:35
a98370d
to
28bd67b
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
3 times, most recently
from
May 21, 2024 22:37
9e06407
to
b5d3089
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
2 times, most recently
from
May 28, 2024 19:47
7d3f899
to
146743a
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
2 times, most recently
from
June 13, 2024 18:06
800fb81
to
c42d2c0
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
2 times, most recently
from
June 28, 2024 07:39
22b56f3
to
9fc3d71
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
from
July 22, 2024 22:31
9fc3d71
to
b9ba6ec
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
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. |
renovate
bot
force-pushed
the
renovate/pre-commit
branch
from
July 24, 2024 23:27
b9ba6ec
to
90680ca
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
from
August 6, 2024 20:32
90680ca
to
6cc5976
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
3 times, most recently
from
August 16, 2024 20:22
c39a90c
to
d9231b4
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
3 times, most recently
from
August 23, 2024 01:14
268a794
to
e337df3
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
2 times, most recently
from
August 28, 2024 17:16
2c5af84
to
3604de0
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
5 times, most recently
from
September 11, 2024 19:48
8dac7f7
to
eac0838
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
from
September 19, 2024 01:32
eac0838
to
3d6ec70
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
2 times, most recently
from
October 3, 2024 16:29
317c185
to
997f32c
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
from
October 8, 2024 22:23
997f32c
to
50a61df
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
from
October 29, 2024 23:28
50a61df
to
ce28a86
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
3 times, most recently
from
November 14, 2024 14:12
2a1d5bc
to
0ac299b
Compare
renovate
bot
force-pushed
the
renovate/pre-commit
branch
from
November 14, 2024 15:01
0ac299b
to
5455130
Compare
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 contains the following updates:
v9.11.0
->v9.18.0
v1.28.1
->v1.47.2
v1.58.1
->v1.62.0
Note: The
pre-commit
manager in Renovate is not supported by thepre-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
v9.17.0
Compare Source
Features
v9.16.0
Compare Source
Features
v9.15.0
Compare Source
Features
v9.14.0
Compare Source
Features
v9.13.0
Compare Source
Features
v9.12.0
Compare Source
Features
bufbuild/buf (bufbuild/buf)
v1.47.2
Compare Source
v1.47.1
Compare Source
v1.47.0
Compare Source
buf registry commit
tobuf registry module commit
. Commandbuf registry commit
is now deprecated.buf registry label
tobuf registry module label
. Commandbuf registry label
is now deprecated.v1.46.0
Compare Source
buf registry whoami
command, which checks if you are logged in to the Buf SchemaRegistry at a given domain.
v1.45.0
Compare Source
buf registry module info --format=json
to adddefault_label_name
, which provides the nameof the default label of a module.
v1.44.0
Compare Source
PROTOVALIDATE
lint rule to check example field options. Examples will be checked thatthey satisfy the field constraints, and are only present if constraints are present.
PROTOVALIDATE
lint rule to check predefined rules. Predefined rules will be checkedthat they compile.
.wasm
file extension to specify a path to a Wasm plugin.v1.43.0
Compare Source
buf beta lsp
.v1.42.0
Compare Source
our launch blog post
for more details!
buf dep graph --format
flag that defaults todot
, and adds the optionjson
, to printthe dependency graph in JSON format.
buf format
where trailing comments on commas in message literals were not properlypropagated 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
buf curl
.v1.40.1
Compare Source
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
buf config ls-{breaking,lint}-rules
. Default rules are those rules which are run if no lintor breaking rules are explicitly configured in your
buf.yaml
.DEFAULT
lint rule category toSTANDARD
. With the concept of default rules being introduced,having a category named
DEFAULT
is confusing, as while it happens that all the rules in theDEFAULT
lint category are also default rules, the name has become overloaded. As with all
buf
changes, thischange is backwards-compatible: the
DEFAULT
lint category continues to work, and always will. Werecommend changing to
STANDARD
, however.v1.39.0
Compare Source
includes
key to module configurations in v2buf.yaml
, accepting a list of directories.includes
is specified, a proto file is considered in the module only if it is in one of thedirectories specified.
includes
andexcludes
keys are specified for a module, a proto file is consideredpart of this module if it is contained in any of the include paths and not in any of the exclude
paths.
buf.yaml
to have the same directory path.v1.38.0
Compare Source
--http3
flag tobuf curl
which forcesbuf curl
to use HTTP/3 as the transport.a path to a module, but contained directories with modules, and the modules would not build.
buf.lock
files whenbuf dep update
does not find new dependenciesto update and there is no existing
buf.lock
.buf push
to push the license file or doc file (e.g.README.md
,LICENSE
) in thesame directory as
buf.yaml
if a module does not have a license file or doc file in themodule's directory.
--path
flag for lint and breaking rules to avoid resolving all fileswithin a module. This change can result in a performance improvement for large workspaces.
v1.37.0
Compare Source
STABLE_PACKAGE_NO_IMPORT_UNSTABLE
lint rule which disallows files from stable packagesto import files from unstable packages.
v1.36.0
Compare Source
--list-services
and--list-methods
flags tobuf curl
, which trigger the command to listknown services or methods in the RPC schema, instead of invoking an RPC method.
clean
as a top-level option inbuf.gen.yaml
, matching thebuf generate --clean
flag. Ifset to true, this will delete the directories, jar files, or zip files set to
out
for eachplugin.
buf registry login
to complete the login flow in the browser by default. This allowsusers to login with their browser and have the token automatically provided to the CLI.
buf registry organization {create, delete, info, update}
commands to manage BSRorganizations. Remove
buf beta registry organization
commands.buf registry module {create, delete, deprecate, info, undeprecate, update}
commands tomanage BSR modules. Remove
buf beta registry repository
commands.buf registry label {archive, info, list, unarchive}
commands to manage BSR module labels.Remove
buf beta registry label
commands andbuf beta registry {archive, unarchive}
.buf registry commit {add-label, info, list, resolve}
to manage BSR module commits. Removebuf beta registry commit
commands.v1.35.1
Compare Source
ref
to align with thegit
notion of a ref. This allows for the useof branch names, tag names, and commit hashes.
buf build
errors with absolute path directory inputs without workspace and/ormodule configurations (e.g.
buf.yaml
,buf.work.yaml
) and proto file paths set to the--path
flag.v1.35.0
Compare Source
buf generate --clean
flag that will delete the directories, jar files, or zip files that theplugins will write to, prior to generation. Allows cleaning of existing assets without having
to call
rm -rf
.--username
flag on and username prompt onbuf registry login
. A username is no longerrequired to log in.
v1.34.0
Compare Source
buf config ls-modules
command to list configured modules.buf generate
would succeed on missing insertion points andpanic on empty insertion point files.
buf generate
to allow the use of Editions syntax when doing local codegeneration by proxying to a
protoc
binary (for languages where code gen isimplemented inside of
protoc
instead of in a plugin: Java, C++, Python, etc).protoc_path
property of forbuf.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
--source-control-url
and--create-default-label
when using--git-metadata
withbuf push
.buf push --git-metadata
when local tags point to different objects thanthe remote tags.
PROTOVALIDATE
lint rule violations.buf beta registry label {create,get,list}
to replacebuf beta registry {draft, tag}
commands.
buf beta commit {get,list}
command outputs to display create time and stopdisplaying associated tags.
buf beta commit list <buf.build/owner/repository>
when thereference is empty. It now lists commits in the repository instead of listing commits
of the default label.
buf format
to canonicalize the punctuation used in message literalsin option values. The output now always uses
{
and}
instead of<
and>
; itadds
:
separators between field names and message values if the source omitted them,and it removes unnecessary separators between fields (
,
and;
are allowed, butneither is needed).
buf format -w
so that it does not touch files whose contents don't actuallychange. This eliminates noisy notifications to file-system-watcher tools that are
watching the directory that contains proto sources.
buf generate
to work with plugins provided by protoc for versions v24.0to 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.
buf push --exclude-unnamed
flag to exclude unnamed modules when pushing to the BSR.v1.32.2
Compare Source
buf generate
to warn instead of error when proto3 optional is required but notsupported by a plugin.
v1.32.1
Compare Source
--path
and--exclude-path
paths are relative tothe
#subdir
rather than the root of the input. This fixes an unintended behavior changethat was introduced in
v1.32.0
.module
input forprotoc-gen-buf-lint
andprotoc-gen-buf-breaking
to allowusers to specify the module for
v2
configuration files.v1.32.0
Compare Source
v2
forbuf.yaml
andbuf.gen.yaml
configuration files.buf config migrate
to migrate configuration files to the latest version (nowv2
).buf mod init
tobuf config init
.buf mod init
is now deprecated.buf mod ls-lint-rules
tobuf config ls-lint-rules
.buf mod ls-lint-rules
is nowdeprecated.
buf mod ls-breaking-rules
tobuf config ls-breaking-rules
.buf mod ls-breaking-rules
is now deprecated.
buf mod prune
tobuf dep prune
.buf mod prune
is now deprecated.buf mod update
tobuf dep update
.buf mod update
is now deprecated.buf mod {clear-cache,cc}
tobuf registry cc
.buf mod {clear-cache,cc}
is nowdeprecated.
buf beta graph
to stable asbuf dep graph
.buf push --create-visibility
toprivate
when the--create
flag is set. Users are no longer required to set
--create-visibility
when runningbuf push --create
.buf push --label
, which allows users to set labels when pushing new commits to the BSR.buf push --source-control-url
, which allows users to associate commits pushed to the BSRwith a URL to a source code repository.
buf push --create-default-label
, which allows users to set a default label for a repositorywhen calling
buf push --create
.buf push --git-metadata
, which automatically sets appropriate--label
,--source-control-url
, and--create-default-label
flags based on the current Git repository.buf convert --validate
to apply protovalidaterules to incoming messages specified with
--from
.buf mod open
.buf beta migrate-v1beta1
This is now replaced withbuf config migrate
.buf registry sdk version
to get the version of a Generated SDK for a module and plugin.buf beta registry archive
andbuf beta registry unarchive
commands for archiving andunarchiving labels on the BSR.
buf
to be used with sources that use edition2023, instead of proto2 or proto3 syntax. This also updates the
protoc-gen-buf-breaking
andprotoc-gen-buf-lint
Protobuf plugins to support files that use edition 2023.buf breaking
rules to work with Protobuf Editions. To support Editions, some rules havebeen deprecated and replaced with Editions-aware rules. All deprecated rules continue to work
for existing users.
FIELD_SAME_CTYPE
has been replaced withFIELD_SAME_CPP_STRING_TYPE
, which considers bothctype
field options and new(pb.cpp).string_type
features when deciding on backwardscompatibility.
FIELD_SAME_LABEL
has been replaced with three rules that all check "cardinality". The newrules can distinguish between maps and other repeated fields and between implicit and explicit
field presence. The new rules are:
FIELD_SAME_CARDINALITY
in theFILE
andPACKAGE
categories.FIELD_WIRE_COMPATIBLE_CARDINALITY
in theWIRE
category.FIELD_WIRE_JSON_COMPATIBLE_CARDINALITY
in theWIRE_JSON
category.FILE_SAME_JAVA_STRING_CHECK_UTF8
has been replaced withFIELD_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.
FILE_SAME_SYNTAX
rule with a few related rules that can catch the samesort of compatibility issues, but in an Editions source file that changes feature values:
MESSAGE_SAME_JSON_FORMAT
andENUM_SAME_JSON_FORMAT
catch changes to thejson_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.
FIELD_SAME_UTF8_VALIDATION
catches changes to theutf8_validation
feature, whichcontrols validation of string values.
ENUM_SAME_TYPE
catches changes to an enum's type, open vs. closed.buf breaking
. All existing rules for fields are now applied toextensions, except for
FIELD_NO_DELETE
(and its variants). There are also newEXTENSION_NO_DELETE
andPACKAGE_EXTENSION_NO_DELETE
rules for catching deletions of anextension. The new rules are not active by default in existing
v1
andv1beta1
configurations, for backwards-compatibility reasons. Migrate your config to
v2
to use them.buf lint
. It previously only checked extensions thatwere defined inside of messages.
FIELD_NOT_REQUIRED
lint rule that prevents use of required in proto2 files and offeatures.field_presence = LEGACY_REQUIRED
in Editions files. This new rule is not active bydefault in existing
v1
andv1beta1
configurations, for backwards-compatibility reasons.Migrate your config to
v2
to use them.v1.31.0
Compare Source
v1.30.1
Compare Source
buf lint
incorrectly reports an error for(buf.validate.field).repeated
is set for a repeated validation rule.
v1.30.0
Compare Source
buf generate
so it populates the recently-addedsource_file_descriptors
field of the
CodeGeneratorRequest
message. This provides the plugin with access to optionsthat 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 wayfor the files named in
file_to_generate
field.--exclude-source-retention-options
flag tobuf build
, whichcauses options configured to only be retained in source to be stripped
from the output descriptors.
v1.29.0
Compare Source
yaml
format. All commands that take image inputs, output images,or convert between message formats, now take
yaml
as a format, in addition tothe existing
binpb
andtxtpb
formats. Some examples:buf build -o image.yaml
buf ls-files image.yaml
buf convert --type foo.Bar --from input.binpb --to output.yaml
yaml
andjson
formats now accept two new options:use_proto_names
anduse_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
buf format
would inadvertently mangle files that usedthe expanded
Any
syntaxin option values.
golangci/golangci-lint (golangci/golangci-lint)
v1.62.0
Compare Source
v1.61.0
Compare Source
junit-xml-extended
formatdupword
: from 0.0.14 to 0.1.1fatcontext
: from 0.4.0 to 0.5.2gci
: from 0.13.4 to 0.13.5 (new optionno-lex-order
)go-ruleguard
: from 0.4.2 to0fe6f58
(fix panic with custom linters)godot
: from 1.4.16 to 1.4.17gomodguard
: from 1.3.3 to 1.3.5gosec
: disable temporarilyG407
gosec
: fromab3f6c1
to 2.21.2 (partially fixG115
)intrange
: from 0.1.2 to 0.2.0nolintlint
: remove the empty line in the directive replacementtypecheck
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
go-errorlint
: from 1.5.1 to 1.5.2gomnd
: deprecated configuration compatibilityintrange
: addstyle
presetmisspell
: from 0.5.1 to 0.6.0sloglint
: from 0.7.0 to 0.7.1testifylint
: from 1.3.0 to 1.3.1unparam
: bump to HEADusestdlibvars
: from 1.25.0 to 1.26.0revive
configurationv1.59.0
Compare Source
v1.58.2
Compare Source
canonicalheader
: from 1.0.6 to 1.1.1gosec
: from 2.19.0 to 2.20.0musttag
: from 0.12.1 to 0.12.2nilnil
: from 0.1.8 to 0.1.9Configuration
📅 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.
This PR was generated by Mend Renovate. View the repository job log.