{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":591425583,"defaultBranch":"main","name":"protobuf-conformance","ownerLogin":"bufbuild","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2023-01-20T18:19:06.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/54191850?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1717616023.0","currentOid":""},"activityList":{"items":[{"before":null,"after":"af83f6e104c51673feafdd5e856450d771569321","ref":"refs/heads/sayers/protobuf_27.1","pushedAt":"2024-06-05T19:33:28.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"smaye81","name":"Steve Ayers","path":"/smaye81","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/911455?s=80&v=4"},"commit":{"message":"Protobuf v27.1","shortMessageHtmlLink":"Protobuf v27.1"}},{"before":"8966830e484faef10aa76edd104d2941c1807fa6","after":null,"ref":"refs/heads/dependabot/npm_and_yarn/impl/ts-proto/ts-proto-50d079ce19","pushedAt":"2024-06-03T14:27:41.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"smaye81","name":"Steve Ayers","path":"/smaye81","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/911455?s=80&v=4"}},{"before":"d8eddd08b7ade554686689c0bb31592fb9f6f066","after":"939bdb8b4251d1c397f964371473f6ed3a7e897b","ref":"refs/heads/main","pushedAt":"2024-06-03T14:27:40.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"smaye81","name":"Steve Ayers","path":"/smaye81","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/911455?s=80&v=4"},"commit":{"message":"Bump the ts-proto group in /impl/ts-proto with 4 updates (#225)\n\nBumps the ts-proto group in /impl/ts-proto with 4 updates:\r\n[ts-proto](https://github.com/stephenh/ts-proto),\r\n[@bufbuild/buf](https://github.com/bufbuild/buf),\r\n[@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node)\r\nand [esbuild](https://github.com/evanw/esbuild).\r\n\r\nUpdates `ts-proto` from 1.174.0 to 1.176.1\r\n Sourced from ts-proto's\r\nreleases. Sourced from ts-proto's\r\nchangelog. Sourced from This release contains the (completely backwards-compatible) next\r\ngeneration of the Buf CLI. The Buf CLI and its associated configuration\r\nhave been completely overhauled to support monorepos as first-class\r\ncitizens. We'd call it a v2 of buf, but it's not. Buf is\r\nenterprise-grade software, and we want you to be minimally impacted. The\r\n To read more about what's new, check out our blog and our docs: ... (truncated) Sourced from ... (truncated) Sourced from esbuild's\r\nreleases. Update support for import assertions and import attributes in node\r\n(#3778) Import assertions (the Did you mean to use "with" instead of "assert"?\r\nRelease notes
\r\n\r\n
\r\nv1.176.1
\r\n1.176.1\r\n(2024-05-25)
\r\nBug Fixes
\r\n\r\n
\r\nv1.176.0
\r\n1.176.0\r\n(2024-05-16)
\r\nFeatures
\r\n\r\nv1.175.1
\r\n1.175.1\r\n(2024-05-15)
\r\nBug Fixes
\r\n\r\nv1.175.0
\r\n1.175.0\r\n(2024-05-13)
\r\nFeatures
\r\n\r\nChangelog
\r\n\r\n
\r\n1.176.1\r\n(2024-05-25)
\r\nBug Fixes
\r\n\r\n
\r\n1.176.0\r\n(2024-05-16)
\r\nFeatures
\r\n\r\n1.175.1\r\n(2024-05-15)
\r\nBug Fixes
\r\n\r\n1.175.0\r\n(2024-05-13)
\r\nFeatures
\r\n\r\nCommits
\r\n\r\n
\r\n63990c0
\r\nchore(release): 1.176.1 [skip ci]d2e75cd
\r\nfix: camelToSnake to respect uppercase words, such as\r\n"GetAPIValue" -> "GET_A...159c984
\r\nchore(release): 1.176.0 [skip ci]0b06554
\r\nfeat: Bump ts-proto-descriptors to latest ts-proto. (#1043)d0096d3
\r\nchore(release): 1.175.1 [skip ci]064665f
\r\nfix: outputSchema=true
when onlyTypes=true
(#1039)23bb2f8
\r\nchore(release): 1.175.0 [skip ci]53d6799
\r\nfeat: optionally output versions used to generate files (#1040)
\r\n\r\nUpdates `@bufbuild/buf` from 1.31.0 to 1.32.2\r\nRelease notes
\r\n@bufbuild/buf
's\r\nreleases.\r\n
\r\nv1.32.2
\r\n\r\n
\r\nbuf generate
to warn instead of error when\r\nproto3 optional is required but not supported by a plugin.v1.32.1
\r\n\r\n
\r\n--path
and\r\n--exclude-path
paths are relative to the\r\n#subdir
rather than the root of the input. This fixes an\r\nunintended behavior change that was introduced in\r\nv1.32.0
.module
input for protoc-gen-buf-lint
\r\nand protoc-gen-buf-breaking
to allow users to specify the\r\nmodule for v2
configuration files.v1.32.0
\r\nv1.32.0
release of buf introduces v2
config\r\nformats for both buf.yaml
and buf.gen.yaml
.\r\nAll your current commands and v1
configuration continue to\r\nwork, so you can upgrade to v2
configuration when\r\nappropriate.\r\n
\r\n
\r\n\r\n
\r\n\r\nv2
for buf.yaml
and\r\nbuf.gen.yaml
configuration files.buf config migrate
to migrate configuration files\r\nto the latest version (now v2
).buf mod init
to buf config init
.\r\nbuf mod init
is now deprecated.buf mod ls-lint-rules
to buf config\r\nls-lint-rules
. buf mod ls-lint-rules
is now\r\ndeprecated.buf mod ls-breaking-rules
to buf config\r\nls-breaking-rules
. buf mod ls-breaking-rules
is now\r\ndeprecated.buf mod prune
to buf dep prune
.\r\nbuf mod prune
is now deprecated.buf mod update
to buf dep update
.\r\nbuf mod update
is now deprecated.buf mod {clear-cache,cc}
to buf registry\r\ncc
. buf mod {clear-cache,cc}
is now deprecated.buf beta graph
to stable as buf dep\r\ngraph
.buf push\r\n--create-visibility
to private
when the\r\n--create
flag is set. Users are no longer required to set\r\n--create-visibility
when running buf push\r\n--create
.buf push --label
, which allows users to set labels\r\nwhen pushing new commits to the BSR.buf push --source-control-url
, which allows users\r\nto associate commits pushed to the BSR with a URL to a source code\r\nrepository.buf push --create-default-label
, which allows users\r\nto set a default label for a repository when calling buf push\r\n--create
.buf push --git-metadata
, which automatically sets\r\nappropriate --label
, --source-control-url
, and\r\n--create-default-label
flags based on the current Git\r\nrepository.buf convert --validate
to apply protovalidate rules\r\nto incoming messages specified with --from
.buf mod open
.buf beta migrate-v1beta1
This is now replaced\r\nwith buf config migrate
.buf registry sdk version
to get the version of a\r\nGenerated SDK for a module and plugin.buf beta registry archive
and buf beta\r\nregistry unarchive
commands for archiving and unarchiving labels\r\non the BSR.buf
to\r\nbe used with sources that use edition 2023, instead of proto2 or proto3\r\nsyntax. This also updates the protoc-gen-buf-breaking
and\r\nprotoc-gen-buf-lint
Protobuf plugins to support files that\r\nuse edition 2023.buf breaking
rules to work with Protobuf\r\nEditions. To support Editions, some rules have been deprecated and\r\nreplaced with Editions-aware rules. All deprecated rules continue to\r\nwork for existing users.\r\n\r\n
\r\nFIELD_SAME_CTYPE
has been replaced with\r\nFIELD_SAME_CPP_STRING_TYPE
, which considers both\r\nctype
field options and new\r\n(pb.cpp).string_type
features when deciding on backwards\r\ncompatibility.FIELD_SAME_LABEL
has been replaced with three rules\r\nthat all check "cardinality". The new rules can distinguish\r\nbetween maps and other repeated fields and between implicit and explicit\r\nfield presence. The new rules are:\r\n\r\n
\r\nFIELD_SAME_CARDINALITY
in the FILE
and\r\nPACKAGE
categories.FIELD_WIRE_COMPATIBLE_CARDINALITY
in the\r\nWIRE
category.FIELD_WIRE_JSON_COMPATIBLE_CARDINALITY
in the\r\nWIRE_JSON
category.FILE_SAME_JAVA_STRING_CHECK_UTF8
has been replaced with\r\nFIELD_SAME_JAVA_UTF8_VALIDATION
, which considers both the\r\njava_string_check_utf8
file option and\r\n(pb.java).utf8_validation
features when deciding on\r\nbackwards compatibility.FILE_SAME_SYNTAX
rule with a few\r\nrelated rules that can catch the same sort of compatibility issues, but\r\nin an Editions source file that changes feature values:\r\n\r\n
\r\nMESSAGE_SAME_JSON_FORMAT
and\r\nENUM_SAME_JSON_FORMAT
catch changes to the\r\njson_format
feature, which controls whether support for the\r\nJSON format is best-effort or properly supported. When supported, the\r\ncompiler performs more checks relating to field name collisions for the\r\nJSON format as well as for FieldMask usage.FIELD_SAME_UTF8_VALIDATION
catches changes to the\r\nutf8_validation
feature, which controls validation of\r\nstring values.ENUM_SAME_TYPE
catches changes to an enum's type, open\r\nvs. closed.buf breaking
. All\r\nexisting rules for fields are now applied to extensions, except for\r\nFIELD_NO_DELETE
(and its variants). There are also new\r\nEXTENSION_NO_DELETE
and\r\nPACKAGE_EXTENSION_NO_DELETE
rules for catching deletions of\r\nan extension. The new rules are not active by default in existing\r\nv1
and v1beta1
configurations, for\r\nbackwards-compatibility reasons. Migrate your config to v2
\r\nto use them.Changelog
\r\n@bufbuild/buf
's\r\nchangelog.\r\n
\r\n[v1.32.2] - 2024-05-28
\r\n\r\n
\r\nbuf generate
to warn instead of error when\r\nproto3 optional is required but not\r\nsupported by a plugin.[v1.32.1] - 2024-05-21
\r\n\r\n
\r\n--path
and\r\n--exclude-path
paths are relative to\r\nthe #subdir
rather than the root of the input. This fixes\r\nan unintended behavior change\r\nthat was introduced in v1.32.0
.module
input for protoc-gen-buf-lint
\r\nand protoc-gen-buf-breaking
to allow\r\nusers to specify the module for v2
configuration\r\nfiles.[v1.32.0] - 2024-05-16
\r\n\r\n
\r\n\r\nv2
for buf.yaml
and\r\nbuf.gen.yaml
configuration files.buf config migrate
to migrate configuration files\r\nto the latest version (now v2
).buf mod init
to buf config init
.\r\nbuf mod init
is now deprecated.buf mod ls-lint-rules
to buf config\r\nls-lint-rules
. buf mod ls-lint-rules
is now\r\ndeprecated.buf mod ls-breaking-rules
to buf config\r\nls-breaking-rules
. buf mod ls-breaking-rules
\r\nis now deprecated.buf mod prune
to buf dep prune
.\r\nbuf mod prune
is now deprecated.buf mod update
to buf dep update
.\r\nbuf mod update
is now deprecated.buf mod {clear-cache,cc}
to buf registry\r\ncc
. buf mod {clear-cache,cc}
is now\r\ndeprecated.buf beta graph
to stable as buf dep\r\ngraph
.buf push\r\n--create-visibility
to private
when the\r\n--create
\r\nflag is set. Users are no longer required to set\r\n--create-visibility
when running\r\nbuf push --create
.buf push --label
, which allows users to set labels\r\nwhen pushing new commits to the BSR.buf push --source-control-url
, which allows users\r\nto associate commits pushed to the BSR\r\nwith a URL to a source code repository.buf push --create-default-label
, which allows users\r\nto set a default label for a repository\r\nwhen calling buf push --create
.buf push --git-metadata
, which automatically sets\r\nappropriate --label
,\r\n--source-control-url
, and\r\n--create-default-label
flags based on the current Git\r\nrepository.buf convert --validate
to apply protovalidate\r\nrules to incoming messages specified with --from
.buf mod open
.buf beta migrate-v1beta1
This is now replaced\r\nwith buf config migrate
.buf registry sdk version
to get the version of a\r\nGenerated SDK for a module and plugin.buf beta registry archive
and buf beta\r\nregistry unarchive
commands for archiving and\r\nunarchiving labels on the BSR.buf
to\r\nbe used with sources that use edition\r\n2023, instead of proto2 or proto3 syntax. This also updates the\r\nprotoc-gen-buf-breaking
and\r\nprotoc-gen-buf-lint
Protobuf plugins to support files that\r\nuse edition 2023.buf breaking
rules to work with Protobuf\r\nEditions. To support Editions, some rules have\r\nbeen deprecated and replaced with Editions-aware rules. All deprecated\r\nrules continue to work\r\nfor existing users.Commits
\r\n\r\n
\r\n47016f1
\r\nRelease v1.32.2 (#3028)0be85d3
\r\nWarn when a plugin does not proto3 optional instead of error-ing (#3015)2dfac93
\r\nSupport annotated tags for push git metadata (#3013)0ebe2de
\r\nFix link to tour (#3027)3765c7d
\r\nBump alpine from 3.19.1 to 3.20.0 (#3018)bf54023
\r\nBump bufbuild/buf-setup-action from 1.32.0 to 1.32.1 (#3017)081013c
\r\nUpdate buf generate long description (#3022)90659b3
\r\nMake upgrade and upgrade dependencies (#3021)1ff6e69
\r\nAvoid building image for buf export
when\r\n--exclude-imports
flag is set (#...09ff5ec
\r\nBump buf.build/gen/go/bufbuild/registry/connectrpc/go from\r\n1.16.1-20240514010...
\r\n\r\nUpdates `@types/node` from 20.12.7 to 20.13.0\r\nCommits
\r\n\r\n
\r\n
\r\n\r\nUpdates `esbuild` from 0.20.2 to 0.21.4\r\nRelease notes
\r\n\r\n
v0.21.4
\r\n\r\n
assert
keyword) have been removed\r\nfrom node starting in v22.0.0. So esbuild will now strip them and\r\ngenerate a warning with --target=node22
or above:▲ [WARNING] The "assert" keyword is not supported\r\nin the configured target environment ("node22")\r\n[assert-to-with]\r\n
\r\nexample.mjs:1:40:\r\n1 │ import json from "esbuild/package.json" assert {\r\ntype: "json" }\r\n │ ~~~~~~\r\n ╵ with\r\n
Import attributes (the with
keyword) have been\r\nbackported to node 18 starting in v18.20.0. So esbuild will no longer\r\nstrip them with --target=node18.N
if N
is 20\r\nor greater.
Fix for await
transform when a label is present
This release fixes a bug where the for await
transform,\r\nwhich wraps the loop in a try
statement, previously failed\r\nto also move the loop's label into the try
statement. This\r\nbug only affects code that uses both of these features in combination.\r\nHere's an example of some affected code:
// Original code\r\nasync function test() {\r\n outer: for await (const x of [Promise.resolve([0, 1])]) {\r\n for (const y of x) if (y) break outer\r\n throw 'fail'\r\n }\r\n}\r\n// Old output (with --target=es6)\r\nfunction test() {\r\nreturn __async(this, null, function* () {\r\nouter: try {\r\nfor (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp,\r\nerror; more = !(temp = yield iter.next()).done; more = false) {\r\nconst x = temp.value;\r\nfor (const y of x) if (y) break outer;\r\nthrow "fail";\r\n}\r\n} catch (temp) {\r\nerror = [temp];\r\n} finally {\r\ntry {\r\nmore && (temp = iter.return) && (yield temp.call(iter));\r\n} finally {\r\nif (error)\r\nthrow error[0];\r\n}\r\n}\r\n
\r\n... (truncated)
\r\n\r\nSourced from esbuild's\r\nchangelog.
\r\n\r\n\r\n0.21.4
\r\n\r\n
\r\n\r\n- \r\n
\r\nUpdate support for import assertions and import attributes in node\r\n(#3778)
\r\nImport assertions (the
\r\nassert
keyword) have been removed\r\nfrom node starting in v22.0.0. So esbuild will now strip them and\r\ngenerate a warning with--target=node22
or above:\r\n▲ [WARNING] The "assert" keyword is not supported\r\nin the configured target environment ("node22")\r\n[assert-to-with]\r\n
\r\nexample.mjs:1:40:\r\n1 │ import json from "esbuild/package.json" assert {\r\ntype: "json" }\r\n │ ~~~~~~\r\n ╵ with\r\n
Did you mean to use "with" instead of "assert"?\r\n
Import attributes (the
\r\nwith
keyword) have been\r\nbackported to node 18 starting in v18.20.0. So esbuild will no longer\r\nstrip them with--target=node18.N
ifN
is 20\r\nor greater.- \r\n
\r\nFix
\r\nfor await
transform when a label is presentThis release fixes a bug where the
\r\nfor await
transform,\r\nwhich wraps the loop in atry
statement, previously failed\r\nto also move the loop's label into thetry
statement. This\r\nbug only affects code that uses both of these features in combination.\r\nHere's an example of some affected code:\r\n// Original code\r\nasync function test() {\r\n outer: for await (const x of [Promise.resolve([0, 1])]) {\r\n for (const y of x) if (y) break outer\r\n throw 'fail'\r\n }\r\n}\r\n
// Old output (with --target=es6)\r\nfunction test() {\r\nreturn __async(this, null, function* () {\r\nouter: try {\r\nfor (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp,\r\nerror; more = !(temp = yield iter.next()).done; more = false) {\r\nconst x = temp.value;\r\nfor (const y of x) if (y) break outer;\r\nthrow "fail";\r\n}\r\n} catch (temp) {\r\nerror = [temp];\r\n} finally {\r\ntry {\r\nmore && (temp = iter.return) && (yield temp.call(iter));\r\n} finally {\r\nif (error)\r\nthrow error[0];\r\n}\r\n
... (truncated)
\r\n67cbf87
\r\npublish 0.21.4 to npm4ad11c3
\r\nfix #3639,\r\nfix #3646:\r\npass with
to onResolve
516ca31
\r\nfix #3343:\r\nallow bundle-internal string aliases9e2f304
\r\nfix #3416,\r\nfix #3425:\r\nbetter enum constant folding8f1faf7
\r\nimplement late constant-folding for && || ??
7d50a50
\r\nimplement late constant-folding of string enums1b29ac7
\r\nfold equality checks after cross-module inliningd7a8bf3
\r\nformatting support for @position-try
(for #3773)5069410
\r\nfix #3778:\r\nimport assertions/attributes for node11d568c
\r\nrun make update-compat-table
Sourced from @bufbuild/protobuf
's\r\nreleases.
\r\n\r\nv1.10.0
\r\nWhat's Changed
\r\n\r\n
\r\n- Skip null values in message initializer object by
\r\n@timostamm
in bufbuild/protobuf-es#862- Fix Node10 subpath fallbacks by
\r\n@timostamm
in bufbuild/protobuf-es#803- Check for matching field numbers in StartGroup / EndGroup tags by
\r\n@smaye81
in bufbuild/protobuf-es#816- Update to google protobuf v27.0 by
\r\n@timostamm
in bufbuild/protobuf-es#854Full Changelog: https://github.com/bufbuild/protobuf-es/compare/v1.9.0...v1.10.0
\r\n
4ab30bf
\r\nRelease 1.10.0 (#865)ff7eaa6
\r\nSkip null values in message initializer object (#862)9120e30
\r\nUpdate to google protobuf v27.0 (#854)48cc09c
\r\nUpdate bundle-size benchmark (#845)ad203dd
\r\nCheck for matching field numbers in StartGroup / EndGroup tags (#816)e1583b4
\r\nFix Node10 subpath fallbacks (#803)Sourced from @bufbuild/protoc-gen-es
's\r\nreleases.
\r\n\r\nv1.10.0
\r\nWhat's Changed
\r\n\r\n
\r\n- Skip null values in message initializer object by
\r\n@timostamm
in bufbuild/protobuf-es#862- Fix Node10 subpath fallbacks by
\r\n@timostamm
in bufbuild/protobuf-es#803- Check for matching field numbers in StartGroup / EndGroup tags by
\r\n@smaye81
in bufbuild/protobuf-es#816- Update to google protobuf v27.0 by
\r\n@timostamm
in bufbuild/protobuf-es#854Full Changelog: https://github.com/bufbuild/protobuf-es/compare/v1.9.0...v1.10.0
\r\n
4ab30bf
\r\nRelease 1.10.0 (#865)e1583b4
\r\nFix Node10 subpath fallbacks (#803)Sourced from @bufbuild/buf
's\r\nreleases.
\r\n\r\nv1.32.2
\r\n\r\n
\r\n- Update
\r\nbuf generate
to warn instead of error when\r\nproto3 optional is required but not supported by a plugin.v1.32.1
\r\n\r\n
\r\n- Fix archive and git inputs so that
\r\n--path
and\r\n--exclude-path
paths are relative to the\r\n#subdir
rather than the root of the input. This fixes an\r\nunintended behavior change that was introduced in\r\nv1.32.0
.- Add
\r\nmodule
input forprotoc-gen-buf-lint
\r\nandprotoc-gen-buf-breaking
to allow users to specify the\r\nmodule forv2
configuration files.v1.32.0
\r\nThis release contains the (completely backwards-compatible) next\r\ngeneration of the Buf CLI. The Buf CLI and its associated configuration\r\nhave been completely overhauled to support monorepos as first-class\r\ncitizens. We'd call it a v2 of buf, but it's not. Buf is\r\nenterprise-grade software, and we want you to be minimally impacted. The\r\n
\r\nv1.32.0
release of buf introducesv2
config\r\nformats for bothbuf.yaml
andbuf.gen.yaml
.\r\nAll your current commands andv1
configuration continue to\r\nwork, so you can upgrade tov2
configuration when\r\nappropriate.To read more about what's new, check out our blog and our docs:
\r\n\r\n
\r\n- Introducing\r\nthe next generation of the Buf CLI: still v1 and\r\nbackwards-compatible
\r\n- Introducing the\r\nnewly improved BSR UI and buf push experience
\r\n- Migrate\r\nto v2 configuration files
\r\n
\r\n\r\n
\r\n\r\n- Add version
\r\nv2
forbuf.yaml
and\r\nbuf.gen.yaml
configuration files.- Add
\r\nbuf config migrate
to migrate configuration files\r\nto the latest version (nowv2
).- Move
\r\nbuf mod init
tobuf config init
.\r\nbuf mod init
is now deprecated.- Move
\r\nbuf mod ls-lint-rules
tobuf config\r\nls-lint-rules
.buf mod ls-lint-rules
is now\r\ndeprecated.- Move
\r\nbuf mod ls-breaking-rules
tobuf config\r\nls-breaking-rules
.buf mod ls-breaking-rules
is now\r\ndeprecated.- Move
\r\nbuf mod prune
tobuf dep prune
.\r\nbuf mod prune
is now deprecated.- Move
\r\nbuf mod update
tobuf dep update
.\r\nbuf mod update
is now deprecated.- Move
\r\nbuf mod {clear-cache,cc}
tobuf registry\r\ncc
.buf mod {clear-cache,cc}
is now deprecated.- Move
\r\nbuf beta graph
to stable asbuf dep\r\ngraph
.- Change the default visibility of
\r\nbuf push\r\n--create-visibility
toprivate
when the\r\n--create
flag is set. Users are no longer required to set\r\n--create-visibility
when runningbuf push\r\n--create
.- Add
\r\nbuf push --label
, which allows users to set labels\r\nwhen pushing new commits to the BSR.- Add
\r\nbuf push --source-control-url
, which allows users\r\nto associate commits pushed to the BSR with a URL to a source code\r\nrepository.- Add
\r\nbuf push --create-default-label
, which allows users\r\nto set a default label for a repository when callingbuf push\r\n--create
.- Add
\r\nbuf push --git-metadata
, which automatically sets\r\nappropriate--label
,--source-control-url
, and\r\n--create-default-label
flags based on the current Git\r\nrepository.- Add
\r\nbuf convert --validate
to apply protovalidate rules\r\nto incoming messages specified with--from
.- Deprecate
\r\nbuf mod open
.- Delete
\r\nbuf beta migrate-v1beta1
This is now replaced\r\nwithbuf config migrate
.- Add
\r\nbuf registry sdk version
to get the version of a\r\nGenerated SDK for a module and plugin.- Add
\r\nbuf beta registry archive
andbuf beta\r\nregistry unarchive
commands for archiving and unarchiving labels\r\non the BSR.- Add support for Protobuf Editions. This allows
\r\nbuf
to\r\nbe used with sources that use edition 2023, instead of proto2 or proto3\r\nsyntax. This also updates theprotoc-gen-buf-breaking
and\r\nprotoc-gen-buf-lint
Protobuf plugins to support files that\r\nuse edition 2023.- Update
\r\nbuf breaking
rules to work with Protobuf\r\nEditions. To support Editions, some rules have been deprecated and\r\nreplaced with Editions-aware rules. All deprecated rules continue to\r\nwork for existing users.\r\n\r\n
\r\n- \r\n
FIELD_SAME_CTYPE
has been replaced with\r\nFIELD_SAME_CPP_STRING_TYPE
, which considers both\r\nctype
field options and new\r\n(pb.cpp).string_type
features when deciding on backwards\r\ncompatibility.- \r\n
FIELD_SAME_LABEL
has been replaced with three rules\r\nthat all check "cardinality". The new rules can distinguish\r\nbetween maps and other repeated fields and between implicit and explicit\r\nfield presence. The new rules are:\r\n\r\n
\r\n- \r\n
FIELD_SAME_CARDINALITY
in theFILE
and\r\nPACKAGE
categories.- \r\n
FIELD_WIRE_COMPATIBLE_CARDINALITY
in the\r\nWIRE
category.- \r\n
FIELD_WIRE_JSON_COMPATIBLE_CARDINALITY
in the\r\nWIRE_JSON
category.- \r\n
FILE_SAME_JAVA_STRING_CHECK_UTF8
has been replaced with\r\nFIELD_SAME_JAVA_UTF8_VALIDATION
, which considers both the\r\njava_string_check_utf8
file option and\r\n(pb.java).utf8_validation
features when deciding on\r\nbackwards compatibility.- Add to the existing
\r\nFILE_SAME_SYNTAX
rule with a few\r\nrelated rules that can catch the same sort of compatibility issues, but\r\nin an Editions source file that changes feature values:\r\n\r\n
\r\n- \r\n
MESSAGE_SAME_JSON_FORMAT
and\r\nENUM_SAME_JSON_FORMAT
catch changes to the\r\njson_format
feature, which controls whether support for the\r\nJSON format is best-effort or properly supported. When supported, the\r\ncompiler performs more checks relating to field name collisions for the\r\nJSON format as well as for FieldMask usage.- \r\n
FIELD_SAME_UTF8_VALIDATION
catches changes to the\r\nutf8_validation
feature, which controls validation of\r\nstring values.- \r\n
ENUM_SAME_TYPE
catches changes to an enum's type, open\r\nvs. closed.- Add support for extensions to
\r\nbuf breaking
. All\r\nexisting rules for fields are now applied to extensions, except for\r\nFIELD_NO_DELETE
(and its variants). There are also new\r\nEXTENSION_NO_DELETE
and\r\nPACKAGE_EXTENSION_NO_DELETE
rules for catching deletions of\r\nan extension. The new rules are not active by default in existing\r\nv1
andv1beta1
configurations, for\r\nbackwards-compatibility reasons. Migrate your config tov2
\r\nto use them.
... (truncated)
\r\nSourced from @bufbuild/buf
's\r\nchangelog.
\r\n\r\n[v1.32.2] - 2024-05-28
\r\n\r\n
\r\n- Update
\r\nbuf generate
to warn instead of error when\r\nproto3 optional is required but not\r\nsupported by a plugin.[v1.32.1] - 2024-05-21
\r\n\r\n
\r\n- Fix archive and git inputs so that
\r\n--path
and\r\n--exclude-path
paths are relative to\r\nthe#subdir
rather than the root of the input. This fixes\r\nan unintended behavior change\r\nthat was introduced inv1.32.0
.- Add
\r\nmodule
input forprotoc-gen-buf-lint
\r\nandprotoc-gen-buf-breaking
to allow\r\nusers to specify the module forv2
configuration\r\nfiles.[v1.32.0] - 2024-05-16
\r\n\r\n
\r\n\r\n- Add version
\r\nv2
forbuf.yaml
and\r\nbuf.gen.yaml
configuration files.- Add
\r\nbuf config migrate
to migrate configuration files\r\nto the latest version (nowv2
).- Move
\r\nbuf mod init
tobuf config init
.\r\nbuf mod init
is now deprecated.- Move
\r\nbuf mod ls-lint-rules
tobuf config\r\nls-lint-rules
.buf mod ls-lint-rules
is now\r\ndeprecated.- Move
\r\nbuf mod ls-breaking-rules
tobuf config\r\nls-breaking-rules
.buf mod ls-breaking-rules
\r\nis now deprecated.- Move
\r\nbuf mod prune
tobuf dep prune
.\r\nbuf mod prune
is now deprecated.- Move
\r\nbuf mod update
tobuf dep update
.\r\nbuf mod update
is now deprecated.- Move
\r\nbuf mod {clear-cache,cc}
tobuf registry\r\ncc
.buf mod {clear-cache,cc}
is now\r\ndeprecated.- Move
\r\nbuf beta graph
to stable asbuf dep\r\ngraph
.- Change the default visibility of
\r\nbuf push\r\n--create-visibility
toprivate
when the\r\n--create
\r\nflag is set. Users are no longer required to set\r\n--create-visibility
when running\r\nbuf push --create
.- Add
\r\nbuf push --label
, which allows users to set labels\r\nwhen pushing new commits to the BSR.- Add
\r\nbuf push --source-control-url
, which allows users\r\nto associate commits pushed to the BSR\r\nwith a URL to a source code repository.- Add
\r\nbuf push --create-default-label
, which allows users\r\nto set a default label for a repository\r\nwhen callingbuf push --create
.- Add
\r\nbuf push --git-metadata
, which automatically sets\r\nappropriate--label
,\r\n--source-control-url
, and\r\n--create-default-label
flags based on the current Git\r\nrepository.- Add
\r\nbuf convert --validate
to apply protovalidate\r\nrules to incoming messages specified with--from
.- Deprecate
\r\nbuf mod open
.- Delete
\r\nbuf beta migrate-v1beta1
This is now replaced\r\nwithbuf config migrate
.- Add
\r\nbuf registry sdk version
to get the version of a\r\nGenerated SDK for a module and plugin.- Add
\r\nbuf beta registry archive
andbuf beta\r\nregistry unarchive
commands for archiving and\r\nunarchiving labels on the BSR.- Add support for Protobuf Editions. This allows
\r\nbuf
to\r\nbe used with sources that use edition\r\n2023, instead of proto2 or proto3 syntax. This also updates the\r\nprotoc-gen-buf-breaking
and\r\nprotoc-gen-buf-lint
Protobuf plugins to support files that\r\nuse edition 2023.- Update
\r\nbuf breaking
rules to work with Protobuf\r\nEditions. To support Editions, some rules have\r\nbeen deprecated and replaced with Editions-aware rules. All deprecated\r\nrules continue to work\r\nfor existing users.
... (truncated)
\r\n47016f1
\r\nRelease v1.32.2 (#3028)0be85d3
\r\nWarn when a plugin does not proto3 optional instead of error-ing (#3015)2dfac93
\r\nSupport annotated tags for push git metadata (#3013)0ebe2de
\r\nFix link to tour (#3027)3765c7d
\r\nBump alpine from 3.19.1 to 3.20.0 (#3018)bf54023
\r\nBump bufbuild/buf-setup-action from 1.32.0 to 1.32.1 (#3017)081013c
\r\nUpdate buf generate long description (#3022)90659b3
\r\nMake upgrade and upgrade dependencies (#3021)1ff6e69
\r\nAvoid building image for buf export
when\r\n--exclude-imports
flag is set (#...09ff5ec
\r\nBump buf.build/gen/go/bufbuild/registry/connectrpc/go from\r\n1.16.1-20240514010...Sourced from tsx's\r\nreleases.
\r\n\r\n\r\nv4.11.0
\r\n4.11.0\r\n(2024-05-23)
\r\nBug Fixes
\r\n\r\nFeatures
\r\n\r\n
\r\n- esm api: configurable
\r\ntsconfig
(3f42ae3)
\r\nThis release is also available on:
\r\n\r\nv4.10.5
\r\n4.10.5\r\n(2024-05-18)
\r\nBug Fixes
\r\n\r\n
\r\nThis release is also available on:
\r\n\r\nv4.10.4
\r\n4.10.4\r\n(2024-05-17)
\r\nBug Fixes
\r\n\r\n
\r\n- cjs: support file url (#18)\r\n(4a8a2dc)
\r\n- V8 coverage support (942e9bc),\r\ncloses privatenumber/tsx#433
\r\n
\r\nThis release is also available on:
\r\n\r\n\r\n
... (truncated)
\r\nb6bf39b
\r\nfix: only error on invalid tsconfig if explicitly passed in (#30)3f42ae3
\r\nfeat(esm api): configurable tsconfig
52d696c
\r\ndocs: use .md extension in linksb54131c
\r\nrefactor: reuse tsconfig utileeaefd6
\r\ntest: separate tsconfig tests9cf2115
\r\ntest: refactor organize fixturesa71c437
\r\nchore: update tsconfig.json86cf87c
\r\nfix: handle parsing variable of
4a8a2dc
\r\nfix(cjs): support file url (#18)942e9bc
\r\nfix: V8 coverage supportSourced from @bufbuild/protobuf
's\r\nreleases.
\r\n\r\nv1.10.0
\r\nWhat's Changed
\r\n\r\n
\r\n- Skip null values in message initializer object by
\r\n@timostamm
in bufbuild/protobuf-es#862- Fix Node10 subpath fallbacks by
\r\n@timostamm
in bufbuild/protobuf-es#803- Check for matching field numbers in StartGroup / EndGroup tags by
\r\n@smaye81
in bufbuild/protobuf-es#816- Update to google protobuf v27.0 by
\r\n@timostamm
in bufbuild/protobuf-es#854Full Changelog: https://github.com/bufbuild/protobuf-es/compare/v1.9.0...v1.10.0
\r\n
4ab30bf
\r\nRelease 1.10.0 (#865)ff7eaa6
\r\nSkip null values in message initializer object (#862)9120e30
\r\nUpdate to google protobuf v27.0 (#854)48cc09c
\r\nUpdate bundle-size benchmark (#845)ad203dd
\r\nCheck for matching field numbers in StartGroup / EndGroup tags (#816)e1583b4
\r\nFix Node10 subpath fallbacks (#803)Sourced from @bufbuild/protoc-gen-es
's\r\nreleases.
\r\n\r\nv1.10.0
\r\nWhat's Changed
\r\n\r\n
\r\n- Skip null values in message initializer object by
\r\n@timostamm
in bufbuild/protobuf-es#862- Fix Node10 subpath fallbacks by
\r\n@timostamm
in bufbuild/protobuf-es#803- Check for matching field numbers in StartGroup / EndGroup tags by
\r\n@smaye81
in bufbuild/protobuf-es#816- Update to google protobuf v27.0 by
\r\n@timostamm
in bufbuild/protobuf-es#854Full Changelog: https://github.com/bufbuild/protobuf-es/compare/v1.9.0...v1.10.0
\r\n
4ab30bf
\r\nRelease 1.10.0 (#865)e1583b4
\r\nFix Node10 subpath fallbacks (#803)Sourced from @bufbuild/buf
's\r\nreleases.
\r\n\r\nv1.32.2
\r\n\r\n
\r\n- Update
\r\nbuf generate
to warn instead of error when\r\nproto3 optional is required but not supported by a plugin.v1.32.1
\r\n\r\n
\r\n- Fix archive and git inputs so that
\r\n--path
and\r\n--exclude-path
paths are relative to the\r\n#subdir
rather than the root of the input. This fixes an\r\nunintended behavior change that was introduced in\r\nv1.32.0
.- Add
\r\nmodule
input forprotoc-gen-buf-lint
\r\nandprotoc-gen-buf-breaking
to allow users to specify the\r\nmodule forv2
configuration files.v1.32.0
\r\nThis release contains the (completely backwards-compatible) next\r\ngeneration of the Buf CLI. The Buf CLI and its associated configuration\r\nhave been completely overhauled to support monorepos as first-class\r\ncitizens. We'd call it a v2 of buf, but it's not. Buf is\r\nenterprise-grade software, and we want you to be minimally impacted. The\r\n
\r\nv1.32.0
release of buf introducesv2
config\r\nformats for bothbuf.yaml
andbuf.gen.yaml
.\r\nAll your current commands andv1
configuration continue to\r\nwork, so you can upgrade tov2
configuration when\r\nappropriate.To read more about what's new, check out our blog and our docs:
\r\n\r\n
\r\n- Introducing\r\nthe next generation of the Buf CLI: still v1 and\r\nbackwards-compatible
\r\n- Introducing the\r\nnewly improved BSR UI and buf push experience
\r\n- Migrate\r\nto v2 configuration files
\r\n
\r\n\r\n
\r\n\r\n- Add version
\r\nv2
forbuf.yaml
and\r\nbuf.gen.yaml
configuration files.- Add
\r\nbuf config migrate
to migrate configuration files\r\nto the latest version (nowv2
).- Move
\r\nbuf mod init
tobuf config init
.\r\nbuf mod init
is now deprecated.- Move
\r\nbuf mod ls-lint-rules
tobuf config\r\nls-lint-rules
.buf mod ls-lint-rules
is now\r\ndeprecated.- Move
\r\nbuf mod ls-breaking-rules
tobuf config\r\nls-breaking-rules
.buf mod ls-breaking-rules
is now\r\ndeprecated.- Move
\r\nbuf mod prune
tobuf dep prune
.\r\nbuf mod prune
is now deprecated.- Move
\r\nbuf mod update
tobuf dep update
.\r\nbuf mod update
is now deprecated.- Move
\r\nbuf mod {clear-cache,cc}
tobuf registry\r\ncc
.buf mod {clear-cache,cc}
is now deprecated.- Move
\r\nbuf beta graph
to stable asbuf dep\r\ngraph
.- Change the default visibility of
\r\nbuf push\r\n--create-visibility
toprivate
when the\r\n--create
flag is set. Users are no longer required to set\r\n--create-visibility
when runningbuf push\r\n--create
.- Add
\r\nbuf push --label
, which allows users to set labels\r\nwhen pushing new commits to the BSR.- Add
\r\nbuf push --source-control-url
, which allows users\r\nto associate commits pushed to the BSR with a URL to a source code\r\nrepository.- Add
\r\nbuf push --create-default-label
, which allows users\r\nto set a default label for a repository when callingbuf push\r\n--create
.- Add
\r\nbuf push --git-metadata
, which automatically sets\r\nappropriate--label
,--source-control-url
, and\r\n--create-default-label
flags based on the current Git\r\nrepository.- Add
\r\nbuf convert --validate
to apply protovalidate rules\r\nto incoming messages specified with--from
.- Deprecate
\r\nbuf mod open
.- Delete
\r\nbuf beta migrate-v1beta1
This is now replaced\r\nwithbuf config migrate
.- Add
\r\nbuf registry sdk version
to get the version of a\r\nGenerated SDK for a module and plugin.- Add
\r\nbuf beta registry archive
andbuf beta\r\nregistry unarchive
commands for archiving and unarchiving labels\r\non the BSR.- Add support for Protobuf Editions. This allows
\r\nbuf
to\r\nbe used with sources that use edition 2023, instead of proto2 or proto3\r\nsyntax. This also updates theprotoc-gen-buf-breaking
and\r\nprotoc-gen-buf-lint
Protobuf plugins to support files that\r\nuse edition 2023.- Update
\r\nbuf breaking
rules to work with Protobuf\r\nEditions. To support Editions, some rules have been deprecated and\r\nreplaced with Editions-aware rules. All deprecated rules continue to\r\nwork for existing users.\r\n\r\n
\r\n- \r\n
FIELD_SAME_CTYPE
has been replaced with\r\nFIELD_SAME_CPP_STRING_TYPE
, which considers both\r\nctype
field options and new\r\n(pb.cpp).string_type
features when deciding on backwards\r\ncompatibility.- \r\n
FIELD_SAME_LABEL
has been replaced with three rules\r\nthat all check "cardinality". The new rules can distinguish\r\nbetween maps and other repeated fields and between implicit and explicit\r\nfield presence. The new rules are:\r\n\r\n
\r\n- \r\n
FIELD_SAME_CARDINALITY
in theFILE
and\r\nPACKAGE
categories.- \r\n
FIELD_WIRE_COMPATIBLE_CARDINALITY
in the\r\nWIRE
category.- \r\n
FIELD_WIRE_JSON_COMPATIBLE_CARDINALITY
in the\r\nWIRE_JSON
category.- \r\n
FILE_SAME_JAVA_STRING_CHECK_UTF8
has been replaced with\r\nFIELD_SAME_JAVA_UTF8_VALIDATION
, which considers both the\r\njava_string_check_utf8
file option and\r\n(pb.java).utf8_validation
features when deciding on\r\nbackwards compatibility.- Add to the existing
\r\nFILE_SAME_SYNTAX
rule with a few\r\nrelated rules that can catch the same sort of compatibility issues, but\r\nin an Editions source file that changes feature values:\r\n\r\n
\r\n- \r\n
MESSAGE_SAME_JSON_FORMAT
and\r\nENUM_SAME_JSON_FORMAT
catch changes to the\r\njson_format
feature, which controls whether support for the\r\nJSON format is best-effort or properly supported. When supported, the\r\ncompiler performs more checks relating to field name collisions for the\r\nJSON format as well as for FieldMask usage.- \r\n
FIELD_SAME_UTF8_VALIDATION
catches changes to the\r\nutf8_validation
feature, which controls validation of\r\nstring values.- \r\n
ENUM_SAME_TYPE
catches changes to an enum's type, open\r\nvs. closed.- Add support for extensions to
\r\nbuf breaking
. All\r\nexisting rules for fields are now applied to extensions, except for\r\nFIELD_NO_DELETE
(and its variants). There are also new\r\nEXTENSION_NO_DELETE
and\r\nPACKAGE_EXTENSION_NO_DELETE
rules for catching deletions of\r\nan extension. The new rules are not active by default in existing\r\nv1
andv1beta1
configurations, for\r\nbackwards-compatibility reasons. Migrate your config tov2
\r\nto use them.
... (truncated)
\r\nSourced from @bufbuild/buf
's\r\nchangelog.
\r\n\r\n[v1.32.2] - 2024-05-28
\r\n\r\n
\r\n- Update
\r\nbuf generate
to warn instead of error when\r\nproto3 optional is required but not\r\nsupported by a plugin.[v1.32.1] - 2024-05-21
\r\n\r\n
\r\n- Fix archive and git inputs so that
\r\n--path
and\r\n--exclude-path
paths are relative to\r\nthe#subdir
rather than the root of the input. This fixes\r\nan unintended behavior change\r\nthat was introduced inv1.32.0
.- Add
\r\nmodule
input forprotoc-gen-buf-lint
\r\nandprotoc-gen-buf-breaking
to allow\r\nusers to specify the module forv2
configuration\r\nfiles.[v1.32.0] - 2024-05-16
\r\n\r\n
\r\n\r\n- Add version
\r\nv2
forbuf.yaml
and\r\nbuf.gen.yaml
configuration files.- Add
\r\nbuf config migrate
to migrate configuration files\r\nto the latest version (nowv2
).- Move
\r\nbuf mod init
tobuf config init
.\r\nbuf mod init
is now deprecated.- Move
\r\nbuf mod ls-lint-rules
tobuf config\r\nls-lint-rules
.buf mod ls-lint-rules
is now\r\ndeprecated.- Move
\r\nbuf mod ls-breaking-rules
tobuf config\r\nls-breaking-rules
.buf mod ls-breaking-rules
\r\nis now deprecated.- Move
\r\nbuf mod prune
tobuf dep prune
.\r\nbuf mod prune
is now deprecated.- Move
\r\nbuf mod update
tobuf dep update
.\r\nbuf mod update
is now deprecated.- Move
\r\nbuf mod {clear-cache,cc}
tobuf registry\r\ncc
.buf mod {clear-cache,cc}
is now\r\ndeprecated.- Move
\r\nbuf beta graph
to stable asbuf dep\r\ngraph
.- Change the default visibility of
\r\nbuf push\r\n--create-visibility
toprivate
when the\r\n--create
\r\nflag is set. Users are no longer required to set\r\n--create-visibility
when running\r\nbuf push --create
.- Add
\r\nbuf push --label
, which allows users to set labels\r\nwhen pushing new commits to the BSR.- Add
\r\nbuf push --source-control-url
, which allows users\r\nto associate commits pushed to the BSR\r\nwith a URL to a source code repository.- Add
\r\nbuf push --create-default-label
, which allows users\r\nto set a default label for a repository\r\nwhen callingbuf push --create
.- Add
\r\nbuf push --git-metadata
, which automatically sets\r\nappropriate--label
,\r\n--source-control-url
, and\r\n--create-default-label
flags based on the current Git\r\nrepository.- Add
\r\nbuf convert --validate
to apply protovalidate\r\nrules to incoming messages specified with--from
.- Deprecate
\r\nbuf mod open
.- Delete
\r\nbuf beta migrate-v1beta1
This is now replaced\r\nwithbuf config migrate
.- Add
\r\nbuf registry sdk version
to get the version of a\r\nGenerated SDK for a module and plugin.- Add
\r\nbuf beta registry archive
andbuf beta\r\nregistry unarchive
commands for archiving and\r\nunarchiving labels on the BSR.- Add support for Protobuf Editions. This allows
\r\nbuf
to\r\nbe used with sources that use edition\r\n2023, instead of proto2 or proto3 syntax. This also updates the\r\nprotoc-gen-buf-breaking
and\r\nprotoc-gen-buf-lint
Protobuf plugins to support files that\r\nuse edition 2023.- Update
\r\nbuf breaking
rules to work with Protobuf\r\nEditions. To support Editions, some rules have\r\nbeen deprecated and replaced with Editions-aware rules. All deprecated\r\nrules continue to work\r\nfor existing users.
... (truncated)
\r\n47016f1
\r\nRelease v1.32.2 (#3028)0be85d3
\r\nWarn when a plugin does not proto3 optional instead of error-ing (#3015)2dfac93
\r\nSupport annotated tags for push git metadata (#3013)0ebe2de
\r\nFix link to tour (#3027)3765c7d
\r\nBump alpine from 3.19.1 to 3.20.0 (#3018)bf54023
\r\nBump bufbuild/buf-setup-action from 1.32.0 to 1.32.1 (#3017)081013c
\r\nUpdate buf generate long description (#3022)90659b3
\r\nMake upgrade and upgrade dependencies (#3021)1ff6e69
\r\nAvoid building image for buf export
when\r\n--exclude-imports
flag is set (#...09ff5ec
\r\nBump buf.build/gen/go/bufbuild/registry/connectrpc/go from\r\n1.16.1-20240514010...Sourced from tsx's\r\nreleases.
\r\n\r\n\r\nv4.11.0
\r\n4.11.0\r\n(2024-05-23)
\r\nBug Fixes
\r\n\r\nFeatures
\r\n\r\n
\r\n- esm api: configurable
\r\ntsconfig
(3f42ae3)
\r\nThis release is also available on:
\r\n\r\nv4.10.5
\r\n4.10.5\r\n(2024-05-18)
\r\nBug Fixes
\r\n\r\n
\r\nThis release is also available on:
\r\n\r\nv4.10.4
\r\n4.10.4\r\n(2024-05-17)
\r\nBug Fixes
\r\n\r\n
\r\n- cjs: support file url (#18)\r\n(4a8a2dc)
\r\n- V8 coverage support (942e9bc),\r\ncloses privatenumber/tsx#433
\r\n
\r\nThis release is also available on:
\r\n\r\n\r\n
... (truncated)
\r\nb6bf39b
\r\nfix: only error on invalid tsconfig if explicitly passed in (#30)3f42ae3
\r\nfeat(esm api): configurable tsconfig
52d696c
\r\ndocs: use .md extension in linksb54131c
\r\nrefactor: reuse tsconfig utileeaefd6
\r\ntest: separate tsconfig tests9cf2115
\r\ntest: refactor organize fixturesa71c437
\r\nchore: update tsconfig.json86cf87c
\r\nfix: handle parsing variable of
4a8a2dc
\r\nfix(cjs): support file url (#18)942e9bc
\r\nfix: V8 coverage supportSourced from protobufjs's\r\nreleases.
\r\n\r\n\r\nprotobufjs: v7.3.0
\r\n7.3.0\r\n(2024-05-10)
\r\nFeatures
\r\n\r\n
Sourced from protobufjs's\r\nchangelog.
\r\n\r\n\r\n7.3.0\r\n(2024-05-10)
\r\nFeatures
\r\n\r\n
722b635
\r\nchore: release master (#1991)2d58011
\r\nfeat: add handling for extension range options (#1990)Sourced from tsx's\r\nreleases.
\r\n\r\n\r\nv4.11.0
\r\n4.11.0\r\n(2024-05-23)
\r\nBug Fixes
\r\n\r\nFeatures
\r\n\r\n
\r\n- esm api: configurable
\r\ntsconfig
(3f42ae3)
\r\nThis release is also available on:
\r\n\r\nv4.10.5
\r\n4.10.5\r\n(2024-05-18)
\r\nBug Fixes
\r\n\r\n
\r\nThis release is also available on:
\r\n\r\nv4.10.4
\r\n4.10.4\r\n(2024-05-17)
\r\nBug Fixes
\r\n\r\n
\r\n- cjs: support file url (#18)\r\n(4a8a2dc)
\r\n- V8 coverage support (942e9bc),\r\ncloses privatenumber/tsx#433
\r\n
\r\nThis release is also available on:
\r\n\r\n\r\n
... (truncated)
\r\nb6bf39b
\r\nfix: only error on invalid tsconfig if explicitly passed in (#30)3f42ae3
\r\nfeat(esm api): configurable tsconfig
52d696c
\r\ndocs: use .md extension in linksb54131c
\r\nrefactor: reuse tsconfig utileeaefd6
\r\ntest: separate tsconfig tests9cf2115
\r\ntest: refactor organize fixturesa71c437
\r\nchore: update tsconfig.json86cf87c
\r\nfix: handle parsing variable of
4a8a2dc
\r\nfix(cjs): support file url (#18)942e9bc
\r\nfix: V8 coverage supportSourced from @bufbuild/buf
's\r\nreleases.
\r\n\r\nv1.32.2
\r\n\r\n
\r\n- Update
\r\nbuf generate
to warn instead of error when\r\nproto3 optional is required but not supported by a plugin.v1.32.1
\r\n\r\n
\r\n- Fix archive and git inputs so that
\r\n--path
and\r\n--exclude-path
paths are relative to the\r\n#subdir
rather than the root of the input. This fixes an\r\nunintended behavior change that was introduced in\r\nv1.32.0
.- Add
\r\nmodule
input forprotoc-gen-buf-lint
\r\nandprotoc-gen-buf-breaking
to allow users to specify the\r\nmodule forv2
configuration files.v1.32.0
\r\nThis release contains the (completely backwards-compatible) next\r\ngeneration of the Buf CLI. The Buf CLI and its associated configuration\r\nhave been completely overhauled to support monorepos as first-class\r\ncitizens. We'd call it a v2 of buf, but it's not. Buf is\r\nenterprise-grade software, and we want you to be minimally impacted. The\r\n
\r\nv1.32.0
release of buf introducesv2
config\r\nformats for bothbuf.yaml
andbuf.gen.yaml
.\r\nAll your current commands andv1
configuration continue to\r\nwork, so you can upgrade tov2
configuration when\r\nappropriate.To read more about what's new, check out our blog and our docs:
\r\n\r\n
\r\n- Introducing\r\nthe next generation of the Buf CLI: still v1 and\r\nbackwards-compatible
\r\n- Introducing the\r\nnewly improved BSR UI and buf push experience
\r\n- Migrate\r\nto v2 configuration files
\r\n
\r\n\r\n
\r\n\r\n- Add version
\r\nv2
forbuf.yaml
and\r\nbuf.gen.yaml
configuration files.- Add
\r\nbuf config migrate
to migrate configuration files\r\nto the latest version (nowv2
).- Move
\r\nbuf mod init
tobuf config init
.\r\nbuf mod init
is now deprecated.- Move
\r\nbuf mod ls-lint-rules
tobuf config\r\nls-lint-rules
.buf mod ls-lint-rules
is now\r\ndeprecated.- Move
\r\nbuf mod ls-breaking-rules
tobuf config\r\nls-breaking-rules
.buf mod ls-breaking-rules
is now\r\ndeprecated.- Move
\r\nbuf mod prune
tobuf dep prune
.\r\nbuf mod prune
is now deprecated.- Move
\r\nbuf mod update
tobuf dep update
.\r\nbuf mod update
is now deprecated.- Move
\r\nbuf mod {clear-cache,cc}
tobuf registry\r\ncc
.buf mod {clear-cache,cc}
is now deprecated.- Move
\r\nbuf beta graph
to stable asbuf dep\r\ngraph
.- Change the default visibility of
\r\nbuf push\r\n--create-visibility
toprivate
when the\r\n--create
flag is set. Users are no longer required to set\r\n--create-visibility
when runningbuf push\r\n--create
.- Add
\r\nbuf push --label
, which allows users to set labels\r\nwhen pushing new commits to the BSR.- Add
\r\nbuf push --source-control-url
, which allows users\r\nto associate commits pushed to the BSR with a URL to a source code\r\nrepository.- Add
\r\nbuf push --create-default-label
, which allows users\r\nto set a default label for a repository when callingbuf push\r\n--create
.- Add
\r\nbuf push --git-metadata
, which automatically sets\r\nappropriate--label
,--source-control-url
, and\r\n--create-default-label
flags based on the current Git\r\nrepository.- Add
\r\nbuf convert --validate
to apply protovalidate rules\r\nto incoming messages specified with--from
.- Deprecate
\r\nbuf mod open
.- Delete
\r\nbuf beta migrate-v1beta1
This is now replaced\r\nwithbuf config migrate
.- Add
\r\nbuf registry sdk version
to get the version of a\r\nGenerated SDK for a module and plugin.- Add
\r\nbuf beta registry archive
andbuf beta\r\nregistry unarchive
commands for archiving and unarchiving labels\r\non the BSR.- Add support for Protobuf Editions. This allows
\r\nbuf
to\r\nbe used with sources that use edition 2023, instead of proto2 or proto3\r\nsyntax. This also updates theprotoc-gen-buf-breaking
and\r\nprotoc-gen-buf-lint
Protobuf plugins to support files that\r\nuse edition 2023.- Update
\r\nbuf breaking
rules to work with Protobuf\r\nEditions. To support Editions, some rules have been deprecated and\r\nreplaced with Editions-aware rules. All deprecated rules continue to\r\nwork for existing users.\r\n\r\n
\r\n- \r\n
FIELD_SAME_CTYPE
has been replaced with\r\nFIELD_SAME_CPP_STRING_TYPE
, which considers both\r\nctype
field options and new\r\n(pb.cpp).string_type
features when deciding on backwards\r\ncompatibility.- \r\n
FIELD_SAME_LABEL
has been replaced with three rules\r\nthat all check "cardinality". The new rules can distinguish\r\nbetween maps and other repeated fields and between implicit and explicit\r\nfield presence. The new rules are:\r\n\r\n
\r\n- \r\n
FIELD_SAME_CARDINALITY
in theFILE
and\r\nPACKAGE
categories.- \r\n
FIELD_WIRE_COMPATIBLE_CARDINALITY
in the\r\nWIRE
category.- \r\n
FIELD_WIRE_JSON_COMPATIBLE_CARDINALITY
in the\r\nWIRE_JSON
category.- \r\n
FILE_SAME_JAVA_STRING_CHECK_UTF8
has been replaced with\r\nFIELD_SAME_JAVA_UTF8_VALIDATION
, which considers both the\r\njava_string_check_utf8
file option and\r\n(pb.java).utf8_validation
features when deciding on\r\nbackwards compatibility.- Add to the existing
\r\nFILE_SAME_SYNTAX
rule with a few\r\nrelated rules that can catch the same sort of compatibility issues, but\r\nin an Editions source file that changes feature values:\r\n\r\n
\r\n- \r\n
MESSAGE_SAME_JSON_FORMAT
and\r\nENUM_SAME_JSON_FORMAT
catch changes to the\r\njson_format
feature, which controls whether support for the\r\nJSON format is best-effort or properly supported. When supported, the\r\ncompiler performs more checks relating to field name collisions for the\r\nJSON format as well as for FieldMask usage.- \r\n
FIELD_SAME_UTF8_VALIDATION
catches changes to the\r\nutf8_validation
feature, which controls validation of\r\nstring values.- \r\n
ENUM_SAME_TYPE
catches changes to an enum's type, open\r\nvs. closed.- Add support for extensions to
\r\nbuf breaking
. All\r\nexisting rules for fields are now applied to extensions, except for\r\nFIELD_NO_DELETE
(and its variants). There are also new\r\nEXTENSION_NO_DELETE
and\r\nPACKAGE_EXTENSION_NO_DELETE
rules for catching deletions of\r\nan extension. The new rules are not active by default in existing\r\nv1
andv1beta1
configurations, for\r\nbackwards-compatibility reasons. Migrate your config tov2
\r\nto use them.
... (truncated)
\r\nSourced from @bufbuild/buf
's\r\nchangelog.
\r\n\r\n[v1.32.2] - 2024-05-28
\r\n\r\n
\r\n- Update
\r\nbuf generate
to warn instead of error when\r\nproto3 optional is required but not\r\nsupported by a plugin.[v1.32.1] - 2024-05-21
\r\n\r\n
\r\n- Fix archive and git inputs so that
\r\n--path
and\r\n--exclude-path
paths are relative to\r\nthe#subdir
rather than the root of the input. This fixes\r\nan unintended behavior change\r\nthat was introduced inv1.32.0
.- Add
\r\nmodule
input forprotoc-gen-buf-lint
\r\nandprotoc-gen-buf-breaking
to allow\r\nusers to specify the module forv2
configuration\r\nfiles.[v1.32.0] - 2024-05-16
\r\n\r\n
\r\n\r\n- Add version
\r\nv2
forbuf.yaml
and\r\nbuf.gen.yaml
configuration files.- Add
\r\nbuf config migrate
to migrate configuration files\r\nto the latest version (nowv2
).- Move
\r\nbuf mod init
tobuf config init
.\r\nbuf mod init
is now deprecated.- Move
\r\nbuf mod ls-lint-rules
tobuf config\r\nls-lint-rules
.buf mod ls-lint-rules
is now\r\ndeprecated.- Move
\r\nbuf mod ls-breaking-rules
tobuf config\r\nls-breaking-rules
.buf mod ls-breaking-rules
\r\nis now deprecated.- Move
\r\nbuf mod prune
tobuf dep prune
.\r\nbuf mod prune
is now deprecated.- Move
\r\nbuf mod update
tobuf dep update
.\r\nbuf mod update
is now deprecated.- Move
\r\nbuf mod {clear-cache,cc}
tobuf registry\r\ncc
.buf mod {clear-cache,cc}
is now\r\ndeprecated.- Move
\r\nbuf beta graph
to stable asbuf dep\r\ngraph
.- Change the default visibility of
\r\nbuf push\r\n--create-visibility
toprivate
when the\r\n--create
\r\nflag is set. Users are no longer required to set\r\n--create-visibility
when running\r\nbuf push --create
.- Add
\r\nbuf push --label
, which allows users to set labels\r\nwhen pushing new commits to the BSR.- Add
\r\nbuf push --source-control-url
, which allows users\r\nto associate commits pushed to the BSR\r\nwith a URL to a source code repository.- Add
\r\nbuf push --create-default-label
, which allows users\r\nto set a default label for a repository\r\nwhen callingbuf push --create
.- Add
\r\nbuf push --git-metadata
, which automatically sets\r\nappropriate--label
,\r\n--source-control-url
, and\r\n--create-default-label
flags based on the current Git\r\nrepository.- Add
\r\nbuf convert --validate
to apply protovalidate\r\nrules to incoming messages specified with--from
.- Deprecate
\r\nbuf mod open
.- Delete
\r\nbuf beta migrate-v1beta1
This is now replaced\r\nwithbuf config migrate
.- Add
\r\nbuf registry sdk version
to get the version of a\r\nGenerated SDK for a module and plugin.- Add
\r\nbuf beta registry archive
andbuf beta\r\nregistry unarchive
commands for archiving and\r\nunarchiving labels on the BSR.- Add support for Protobuf Editions. This allows
\r\nbuf
to\r\nbe used with sources that use edition\r\n2023, instead of proto2 or proto3 syntax. This also updates the\r\nprotoc-gen-buf-breaking
and\r\nprotoc-gen-buf-lint
Protobuf plugins to support files that\r\nuse edition 2023.- Update
\r\nbuf breaking
rules to work with Protobuf\r\nEditions. To support Editions, some rules have\r\nbeen deprecated and replaced with Editions-aware rules. All deprecated\r\nrules continue to work\r\nfor existing users.
... (truncated)
\r\n47016f1
\r\nRelease v1.32.2 (#3028)0be85d3
\r\nWarn when a plugin does not proto3 optional instead of error-ing (#3015)2dfac93
\r\nSupport annotated tags for push git metadata (#3013)0ebe2de
\r\nFix link to tour (#3027)3765c7d
\r\nBump alpine from 3.19.1 to 3.20.0 (#3018)bf54023
\r\nBump bufbuild/buf-setup-action from 1.32.0 to 1.32.1 (#3017)081013c
\r\nUpdate buf generate long description (#3022)90659b3
\r\nMake upgrade and upgrade dependencies (#3021)1ff6e69
\r\nAvoid building image for buf export
when\r\n--exclude-imports
flag is set (#...09ff5ec
\r\nBump buf.build/gen/go/bufbuild/registry/connectrpc/go from\r\n1.16.1-20240514010...Sourced from @bufbuild/buf
's\r\nreleases.
\r\n\r\nv1.32.2
\r\n\r\n
\r\n- Update
\r\nbuf generate
to warn instead of error when\r\nproto3 optional is required but not supported by a plugin.v1.32.1
\r\n\r\n
\r\n- Fix archive and git inputs so that
\r\n--path
and\r\n--exclude-path
paths are relative to the\r\n#subdir
rather than the root of the input. This fixes an\r\nunintended behavior change that was introduced in\r\nv1.32.0
.- Add
\r\nmodule
input forprotoc-gen-buf-lint
\r\nandprotoc-gen-buf-breaking
to allow users to specify the\r\nmodule forv2
configuration files.v1.32.0
\r\nThis release contains the (completely backwards-compatible) next\r\ngeneration of the Buf CLI. The Buf CLI and its associated configuration\r\nhave been completely overhauled to support monorepos as first-class\r\ncitizens. We'd call it a v2 of buf, but it's not. Buf is\r\nenterprise-grade software, and we want you to be minimally impacted. The\r\n
\r\nv1.32.0
release of buf introducesv2
config\r\nformats for bothbuf.yaml
andbuf.gen.yaml
.\r\nAll your current commands andv1
configuration continue to\r\nwork, so you can upgrade tov2
configuration when\r\nappropriate.To read more about what's new, check out our blog and our docs:
\r\n\r\n
\r\n- Introducing\r\nthe next generation of the Buf CLI: still v1 and\r\nbackwards-compatible
\r\n- Introducing the\r\nnewly improved BSR UI and buf push experience
\r\n- Migrate\r\nto v2 configuration files
\r\n
\r\n\r\n
\r\n\r\n- Add version
\r\nv2
forbuf.yaml
and\r\nbuf.gen.yaml
configuration files.- Add
\r\nbuf config migrate
to migrate configuration files\r\nto the latest version (nowv2
).- Move
\r\nbuf mod init
tobuf config init
.\r\nbuf mod init
is now deprecated.- Move
\r\nbuf mod ls-lint-rules
tobuf config\r\nls-lint-rules
.buf mod ls-lint-rules
is now\r\ndeprecated.- Move
\r\nbuf mod ls-breaking-rules
tobuf config\r\nls-breaking-rules
.buf mod ls-breaking-rules
is now\r\ndeprecated.- Move
\r\nbuf mod prune
tobuf dep prune
.\r\nbuf mod prune
is now deprecated.- Move
\r\nbuf mod update
tobuf dep update
.\r\nbuf mod update
is now deprecated.- Move
\r\nbuf mod {clear-cache,cc}
tobuf registry\r\ncc
.buf mod {clear-cache,cc}
is now deprecated.- Move
\r\nbuf beta graph
to stable asbuf dep\r\ngraph
.- Change the default visibility of
\r\nbuf push\r\n--create-visibility
toprivate
when the\r\n--create
flag is set. Users are no longer required to set\r\n--create-visibility
when runningbuf push\r\n--create
.- Add
\r\nbuf push --label
, which allows users to set labels\r\nwhen pushing new commits to the BSR.- Add
\r\nbuf push --source-control-url
, which allows users\r\nto associate commits pushed to the BSR with a URL to a source code\r\nrepository.- Add
\r\nbuf push --create-default-label
, which allows users\r\nto set a default label for a repository when callingbuf push\r\n--create
.- Add
\r\nbuf push --git-metadata
, which automatically sets\r\nappropriate--label
,--source-control-url
, and\r\n--create-default-label
flags based on the current Git\r\nrepository.- Add
\r\nbuf convert --validate
to apply protovalidate rules\r\nto incoming messages specified with--from
.- Deprecate
\r\nbuf mod open
.- Delete
\r\nbuf beta migrate-v1beta1
This is now replaced\r\nwithbuf config migrate
.- Add
\r\nbuf registry sdk version
to get the version of a\r\nGenerated SDK for a module and plugin.- Add
\r\nbuf beta registry archive
andbuf beta\r\nregistry unarchive
commands for archiving and unarchiving labels\r\non the BSR.- Add support for Protobuf Editions. This allows
\r\nbuf
to\r\nbe used with sources that use edition 2023, instead of proto2 or proto3\r\nsyntax. This also updates theprotoc-gen-buf-breaking
and\r\nprotoc-gen-buf-lint
Protobuf plugins to support files that\r\nuse edition 2023.- Update
\r\nbuf breaking
rules to work with Protobuf\r\nEditions. To support Editions, some rules have been deprecated and\r\nreplaced with Editions-aware rules. All deprecated rules continue to\r\nwork for existing users.\r\n\r\n
\r\n- \r\n
FIELD_SAME_CTYPE
has been replaced with\r\nFIELD_SAME_CPP_STRING_TYPE
, which considers both\r\nctype
field options and new\r\n(pb.cpp).string_type
features when deciding on backwards\r\ncompatibility.- \r\n
FIELD_SAME_LABEL
has been replaced with three rules\r\nthat all check "cardinality". The new rules can distinguish\r\nbetween maps and other repeated fields and between implicit and explicit\r\nfield presence. The new rules are:\r\n\r\n
\r\n- \r\n
FIELD_SAME_CARDINALITY
in theFILE
and\r\nPACKAGE
categories.- \r\n
FIELD_WIRE_COMPATIBLE_CARDINALITY
in the\r\nWIRE
category.- \r\n
FIELD_WIRE_JSON_COMPATIBLE_CARDINALITY
in the\r\nWIRE_JSON
category.- \r\n
FILE_SAME_JAVA_STRING_CHECK_UTF8
has been replaced with\r\nFIELD_SAME_JAVA_UTF8_VALIDATION
, which considers both the\r\njava_string_check_utf8
file option and\r\n(pb.java).utf8_validation
features when deciding on\r\nbackwards compatibility.- Add to the existing
\r\nFILE_SAME_SYNTAX
rule with a few\r\nrelated rules that can catch the same sort of compatibility issues, but\r\nin an Editions source file that changes feature values:\r\n\r\n
\r\n- \r\n
MESSAGE_SAME_JSON_FORMAT
and\r\nENUM_SAME_JSON_FORMAT
catch changes to the\r\njson_format
feature, which controls whether support for the\r\nJSON format is best-effort or properly supported. When supported, the\r\ncompiler performs more checks relating to field name collisions for the\r\nJSON format as well as for FieldMask usage.- \r\n
FIELD_SAME_UTF8_VALIDATION
catches changes to the\r\nutf8_validation
feature, which controls validation of\r\nstring values.- \r\n
ENUM_SAME_TYPE
catches changes to an enum's type, open\r\nvs. closed.- Add support for extensions to
\r\nbuf breaking
. All\r\nexisting rules for fields are now applied to extensions, except for\r\nFIELD_NO_DELETE
(and its variants). There are also new\r\nEXTENSION_NO_DELETE
and\r\nPACKAGE_EXTENSION_NO_DELETE
rules for catching deletions of\r\nan extension. The new rules are not active by default in existing\r\nv1
andv1beta1
configurations, for\r\nbackwards-compatibility reasons. Migrate your config tov2
\r\nto use them.
... (truncated)
\r\nSourced from @bufbuild/buf
's\r\nchangelog.
\r\n\r\n[v1.32.2] - 2024-05-28
\r\n\r\n
\r\n- Update
\r\nbuf generate
to warn instead of error when\r\nproto3 optional is required but not\r\nsupported by a plugin.[v1.32.1] - 2024-05-21
\r\n\r\n
\r\n- Fix archive and git inputs so that
\r\n--path
and\r\n--exclude-path
paths are relative to\r\nthe#subdir
rather than the root of the input. This fixes\r\nan unintended behavior change\r\nthat was introduced inv1.32.0
.- Add
\r\nmodule
input forprotoc-gen-buf-lint
\r\nandprotoc-gen-buf-breaking
to allow\r\nusers to specify the module forv2
configuration\r\nfiles.[v1.32.0] - 2024-05-16
\r\n\r\n
\r\n\r\n- Add version
\r\nv2
forbuf.yaml
and\r\nbuf.gen.yaml
configuration files.- Add
\r\nbuf config migrate
to migrate configuration files\r\nto the latest version (nowv2
).- Move
\r\nbuf mod init
tobuf config init
.\r\nbuf mod init
is now deprecated.- Move
\r\nbuf mod ls-lint-rules
tobuf config\r\nls-lint-rules
.buf mod ls-lint-rules
is now\r\ndeprecated.- Move
\r\nbuf mod ls-breaking-rules
tobuf config\r\nls-breaking-rules
.buf mod ls-breaking-rules
\r\nis now deprecated.- Move
\r\nbuf mod prune
tobuf dep prune
.\r\nbuf mod prune
is now deprecated.- Move
\r\nbuf mod update
tobuf dep update
.\r\nbuf mod update
is now deprecated.- Move
\r\nbuf mod {clear-cache,cc}
tobuf registry\r\ncc
.buf mod {clear-cache,cc}
is now\r\ndeprecated.- Move
\r\nbuf beta graph
to stable asbuf dep\r\ngraph
.- Change the default visibility of
\r\nbuf push\r\n--create-visibility
toprivate
when the\r\n--create
\r\nflag is set. Users are no longer required to set\r\n--create-visibility
when running\r\nbuf push --create
.- Add
\r\nbuf push --label
, which allows users to set labels\r\nwhen pushing new commits to the BSR.- Add
\r\nbuf push --source-control-url
, which allows users\r\nto associate commits pushed to the BSR\r\nwith a URL to a source code repository.- Add
\r\nbuf push --create-default-label
, which allows users\r\nto set a default label for a repository\r\nwhen callingbuf push --create
.- Add
\r\nbuf push --git-metadata
, which automatically sets\r\nappropriate--label
,\r\n--source-control-url
, and\r\n--create-default-label
flags based on the current Git\r\nrepository.- Add
\r\nbuf convert --validate
to apply protovalidate\r\nrules to incoming messages specified with--from
.- Deprecate
\r\nbuf mod open
.- Delete
\r\nbuf beta migrate-v1beta1
This is now replaced\r\nwithbuf config migrate
.- Add
\r\nbuf registry sdk version
to get the version of a\r\nGenerated SDK for a module and plugin.- Add
\r\nbuf beta registry archive
andbuf beta\r\nregistry unarchive
commands for archiving and\r\nunarchiving labels on the BSR.- Add support for Protobuf Editions. This allows
\r\nbuf
to\r\nbe used with sources that use edition\r\n2023, instead of proto2 or proto3 syntax. This also updates the\r\nprotoc-gen-buf-breaking
and\r\nprotoc-gen-buf-lint
Protobuf plugins to support files that\r\nuse edition 2023.- Update
\r\nbuf breaking
rules to work with Protobuf\r\nEditions. To support Editions, some rules have\r\nbeen deprecated and replaced with Editions-aware rules. All deprecated\r\nrules continue to work\r\nfor existing users.
... (truncated)
\r\n47016f1
\r\nRelease v1.32.2 (#3028)0be85d3
\r\nWarn when a plugin does not proto3 optional instead of error-ing (#3015)2dfac93
\r\nSupport annotated tags for push git metadata (#3013)0ebe2de
\r\nFix link to tour (#3027)3765c7d
\r\nBump alpine from 3.19.1 to 3.20.0 (#3018)bf54023
\r\nBump bufbuild/buf-setup-action from 1.32.0 to 1.32.1 (#3017)081013c
\r\nUpdate buf generate long description (#3022)90659b3
\r\nMake upgrade and upgrade dependencies (#3021)1ff6e69
\r\nAvoid building image for buf export
when\r\n--exclude-imports
flag is set (#...09ff5ec
\r\nBump buf.build/gen/go/bufbuild/registry/connectrpc/go from\r\n1.16.1-20240514010...Sourced from tsx's\r\nreleases.
\r\n\r\n\r\nv4.11.0
\r\n4.11.0\r\n(2024-05-23)
\r\nBug Fixes
\r\n\r\nFeatures
\r\n\r\n
\r\n- esm api: configurable
\r\ntsconfig
(3f42ae3)
\r\nThis release is also available on:
\r\n\r\nv4.10.5
\r\n4.10.5\r\n(2024-05-18)
\r\nBug Fixes
\r\n\r\n
\r\nThis release is also available on:
\r\n\r\nv4.10.4
\r\n4.10.4\r\n(2024-05-17)
\r\nBug Fixes
\r\n\r\n
\r\n- cjs: support file url (#18)\r\n(4a8a2dc)
\r\n- V8 coverage support (942e9bc),\r\ncloses privatenumber/tsx#433
\r\n
\r\nThis release is also available on:
\r\n\r\n\r\n
... (truncated)
\r\nb6bf39b
\r\nfix: only error on invalid tsconfig if explicitly passed in (#30)3f42ae3
\r\nfeat(esm api): configurable tsconfig
52d696c
\r\ndocs: use .md extension in linksb54131c
\r\nrefactor: reuse tsconfig utileeaefd6
\r\ntest: separate tsconfig tests9cf2115
\r\ntest: refactor organize fixturesa71c437
\r\nchore: update tsconfig.json86cf87c
\r\nfix: handle parsing variable of
4a8a2dc
\r\nfix(cjs): support file url (#18)942e9bc
\r\nfix: V8 coverage supportSourced from ts-proto's\r\nreleases.
\r\n\r\n\r\nv1.174.0
\r\n1.174.0\r\n(2024-05-01)
\r\nFeatures
\r\n\r\nv1.173.0
\r\n1.173.0\r\n(2024-04-30)
\r\nFeatures
\r\n\r\nv1.172.0
\r\n1.172.0\r\n(2024-04-13)
\r\nFeatures
\r\n\r\n
Sourced from ts-proto's\r\nchangelog.
\r\n\r\n\r\n1.174.0\r\n(2024-05-01)
\r\nFeatures
\r\n\r\n1.173.0\r\n(2024-04-30)
\r\nFeatures
\r\n\r\n1.172.0\r\n(2024-04-13)
\r\nFeatures
\r\n\r\n
d444507
\r\nchore(release): 1.174.0 [skip ci]cdd4a76
\r\nfeat: add generated code comments (#1037)577def4
\r\ndocs: add useJsTypeOverride to README (#1036)7da4233
\r\nchore(release): 1.173.0 [skip ci]0dd951b
\r\nfeat: Add js type support (#1030)bd56caf
\r\nchore(deps): update tsx (#1035)7c3ac9f
\r\ndocs: add OneofValue type helper (#1034)7f36a59
\r\nci: update GitHub actions (#1031)6b6115a
\r\nchore(release): 1.172.0 [skip ci]9652586
\r\nfeat: export options types (#1027)Sourced from @bufbuild/buf
's\r\nreleases.
\r\n\r\nv1.31.0
\r\n\r\n
\r\n- Update dependencies.
\r\nv1.30.1
\r\n\r\n
\r\n- Fix issue where
\r\nbuf lint
incorrectly reports an error\r\nfor(buf.validate.field).repeated
\r\nis set for a repeated validation rule.
Sourced from @bufbuild/buf
's\r\nchangelog.
\r\n\r\n[v1.31.0] - 2024-04-23
\r\n\r\n
\r\n- Update dependencies.
\r\n[v1.30.1] - 2024-04-03
\r\n\r\n
\r\n- Fix issue where
\r\nbuf lint
incorrectly reports an error\r\nfor(buf.validate.field).repeated
\r\nis set for a repeated validation rule.
c9863a6
\r\nRelease v1.31.0 (#2908)00dfa3d
\r\nBump connectrpc.com/connect from 1.16.0 to 1.16.1 (#2904)5370d4a
\r\nMake upgrade (#2905)1607d07
\r\nUpdate user_id
to reserved in UserPluginPreferences (#2898)0b24de2
\r\nMake upgrade (#2892)a52805a
\r\nMake upgrade (#2880)e9aaa1b
\r\nBump bufbuild/buf-setup-action from 1.30.0 to 1.30.1 (#2878)5a71edd
\r\nReturn to development (#2866)a3f5940
\r\nRelease v1.30.1 (#2865)aeb84da
\r\nUpdate CHANGELOG.md for v1.30.1 (#2864)Sourced from typescript's\r\nreleases.
\r\n\r\n\r\nTypeScript 5.4.5
\r\nFor release notes, check out the release\r\nannouncement.
\r\nFor the complete list of fixed issues, check out the
\r\n\r\n
\r\n- fixed\r\nissues query for Typescript 5.4.0 (Beta).
\r\n- fixed\r\nissues query for Typescript 5.4.1 (RC).
\r\n- fixed\r\nissues query for Typescript 5.4.2 (Stable).
\r\n- fixed\r\nissues query for Typescript 5.4.3 (Stable).
\r\n- fixed\r\nissues query for Typescript 5.4.4 (Stable).
\r\n- fixed\r\nissues query for Typescript 5.4.5 (Stable).
\r\nDownloads are available on:
\r\n\r\n
\r\n- NuGet\r\npackage
\r\nTypeScript 5.4.4
\r\nFor release notes, check out the release\r\nannouncement.
\r\nFor the complete list of fixed issues, check out the
\r\n\r\n
\r\n- fixed\r\nissues query for Typescript 5.4.0 (Beta).
\r\n- fixed\r\nissues query for Typescript 5.4.1 (RC).
\r\n- fixed\r\nissues query for Typescript 5.4.2 (Stable).
\r\n- fixed\r\nissues query for Typescript 5.4.3 (Stable).
\r\n- fixed\r\nissues query for Typescript 5.4.4 (Stable).
\r\nDownloads are available on:
\r\n\r\n
\r\n- NuGet\r\npackage
\r\n
27bcd4c
\r\nUpdate LKG9f33bf1
\r\n🤖 Pick PR #58098\r\n(Fix constraints of nested homomorph...) into release-5.4 (#...71b2f84
\r\nBump version to 5.4.5 and LKG892936f
\r\n🤖 Pick PR #58083\r\n(Don't propagate partial union/inter...) into release-5.4 (#...38a7c05
\r\nrelease-5.4: Always set node-version for setup-node (#58117)b754fc3
\r\n🤖 Pick PR #57778\r\n(fix type import check for default-i...) into release-5.4 (#...8eb3367
\r\nBump version to 5.4.4 and LKGde9096b
\r\n🤖 Pick PR #57871\r\n(Divide-and-conquer strategy for int...) into release-5.4 (#...06aae98
\r\n🤖 Pick PR #57973\r\n(Compare package.json paths with cor...) into release-5.4 (#...6d8134e
\r\n🤖 Pick PR #57637\r\n(Fixed a regression related to deter...) into release-5.4 (#...Sourced from ts-proto's\r\nreleases.
\r\n\r\n\r\nv1.174.0
\r\n1.174.0\r\n(2024-05-01)
\r\nFeatures
\r\n\r\nv1.173.0
\r\n1.173.0\r\n(2024-04-30)
\r\nFeatures
\r\n\r\nv1.172.0
\r\n1.172.0\r\n(2024-04-13)
\r\nFeatures
\r\n\r\n
Sourced from ts-proto's\r\nchangelog.
\r\n\r\n\r\n1.174.0\r\n(2024-05-01)
\r\nFeatures
\r\n\r\n1.173.0\r\n(2024-04-30)
\r\nFeatures
\r\n\r\n1.172.0\r\n(2024-04-13)
\r\nFeatures
\r\n\r\n
d444507
\r\nchore(release): 1.174.0 [skip ci]cdd4a76
\r\nfeat: add generated code comments (#1037)577def4
\r\ndocs: add useJsTypeOverride to README (#1036)7da4233
\r\nchore(release): 1.173.0 [skip ci]0dd951b
\r\nfeat: Add js type support (#1030)bd56caf
\r\nchore(deps): update tsx (#1035)7c3ac9f
\r\ndocs: add OneofValue type helper (#1034)7f36a59
\r\nci: update GitHub actions (#1031)6b6115a
\r\nchore(release): 1.172.0 [skip ci]9652586
\r\nfeat: export options types (#1027)Sourced from @bufbuild/buf
's\r\nreleases.
\r\n\r\nv1.31.0
\r\n\r\n
\r\n- Update dependencies.
\r\nv1.30.1
\r\n\r\n
\r\n- Fix issue where
\r\nbuf lint
incorrectly reports an error\r\nfor(buf.validate.field).repeated
\r\nis set for a repeated validation rule.
Sourced from @bufbuild/buf
's\r\nchangelog.
\r\n\r\n[v1.31.0] - 2024-04-23
\r\n\r\n
\r\n- Update dependencies.
\r\n[v1.30.1] - 2024-04-03
\r\n\r\n
\r\n- Fix issue where
\r\nbuf lint
incorrectly reports an error\r\nfor(buf.validate.field).repeated
\r\nis set for a repeated validation rule.
c9863a6
\r\nRelease v1.31.0 (#2908)00dfa3d
\r\nBump connectrpc.com/connect from 1.16.0 to 1.16.1 (#2904)5370d4a
\r\nMake upgrade (#2905)1607d07
\r\nUpdate user_id
to reserved in UserPluginPreferences (#2898)0b24de2
\r\nMake upgrade (#2892)a52805a
\r\nMake upgrade (#2880)e9aaa1b
\r\nBump bufbuild/buf-setup-action from 1.30.0 to 1.30.1 (#2878)5a71edd
\r\nReturn to development (#2866)a3f5940
\r\nRelease v1.30.1 (#2865)aeb84da
\r\nUpdate CHANGELOG.md for v1.30.1 (#2864)Sourced from typescript's\r\nreleases.
\r\n\r\n\r\nTypeScript 5.4.5
\r\nFor release notes, check out the release\r\nannouncement.
\r\nFor the complete list of fixed issues, check out the
\r\n\r\n
\r\n- fixed\r\nissues query for Typescript 5.4.0 (Beta).
\r\n- fixed\r\nissues query for Typescript 5.4.1 (RC).
\r\n- fixed\r\nissues query for Typescript 5.4.2 (Stable).
\r\n- fixed\r\nissues query for Typescript 5.4.3 (Stable).
\r\n- fixed\r\nissues query for Typescript 5.4.4 (Stable).
\r\n- fixed\r\nissues query for Typescript 5.4.5 (Stable).
\r\nDownloads are available on:
\r\n\r\n
\r\n- NuGet\r\npackage
\r\nTypeScript 5.4.4
\r\nFor release notes, check out the release\r\nannouncement.
\r\nFor the complete list of fixed issues, check out the
\r\n\r\n
\r\n- fixed\r\nissues query for Typescript 5.4.0 (Beta).
\r\n- fixed\r\nissues query for Typescript 5.4.1 (RC).
\r\n- fixed\r\nissues query for Typescript 5.4.2 (Stable).
\r\n- fixed\r\nissues query for Typescript 5.4.3 (Stable).
\r\n- fixed\r\nissues query for Typescript 5.4.4 (Stable).
\r\nDownloads are available on:
\r\n\r\n
\r\n- NuGet\r\npackage
\r\n
27bcd4c
\r\nUpdate LKG9f33bf1
\r\n🤖 Pick PR #58098\r\n(Fix constraints of nested homomorph...) into release-5.4 (#...71b2f84
\r\nBump version to 5.4.5 and LKG892936f
\r\n🤖 Pick PR #58083\r\n(Don't propagate partial union/inter...) into release-5.4 (#...38a7c05
\r\nrelease-5.4: Always set node-version for setup-node (#58117)b754fc3
\r\n🤖 Pick PR #57778\r\n(fix type import check for default-i...) into release-5.4 (#...8eb3367
\r\nBump version to 5.4.4 and LKGde9096b
\r\n🤖 Pick PR #57871\r\n(Divide-and-conquer strategy for int...) into release-5.4 (#...06aae98
\r\n🤖 Pick PR #57973\r\n(Compare package.json paths with cor...) into release-5.4 (#...6d8134e
\r\n🤖 Pick PR #57637\r\n(Fixed a regression related to deter...) into release-5.4 (#...