The explicitly specified package name is invalid since it identical
to one of the keywords in Go (e.g., "package" or "type").
Remove explicitly specifying the name, which will cause protoc-gen-go
to derive the package name from the last path segment.
If the name is not valid, it will automatically sanitize it
to produce a valid package identifier (e.g., "_package" or "_type").
Committer: @dsnet
PiperOrigin-RevId: 370589666
- added support for GenericSignedAttestation which has a generic Signature
- added support for CVSSv3 and WindowsDetail in Vulnerability
- documentation updates
PiperOrigin-RevId: 286008145
This makes googleapis forward compatible with Bazel incompatible change https://github.com/bazelbuild/bazel/issues/8922.
This CL was created by adding @rules_proto to the WORKSPACE file and then running:
find . -name BUILD.bazel | \
while read build; do \
buildifier --lint=fix --warnings=load $build; \
done
Since buildifier cannot be told not to reformat the BUILD file, some files are reformatted.
PiperOrigin-RevId: 280356106
