debian-forge-composer/vendor/cloud.google.com/go/internal
Ondřej Budai 4499356bfd go.mod: bump osbuild/images to c2aa82cc9a86
images 0.1.0 and 0.2.0 were already released, but they are incompatible with
osbuild-composer's test suite. However, we need to support F40 as soon as
possible. This commit as a workaround: it bumps the dependency to a new enough
version that has Fedora 40, but it's old enough that it doesn't have
the breaking changes.
2023-08-22 10:12:13 +02:00
..
optional internal/upload: Add support for upload to GCP and CLI tool using it 2021-02-25 18:44:21 +00:00
trace build(deps): bump cloud.google.com/go/storage from 1.16.1 to 1.18.1 2021-10-18 07:54:09 +01:00
version internal/upload: Add support for upload to GCP and CLI tool using it 2021-02-25 18:44:21 +00:00
.repo-metadata-full.json go.mod: bump osbuild/images to c2aa82cc9a86 2023-08-22 10:12:13 +02:00
annotate.go build(deps): bump cloud.google.com/go/storage from 1.26.0 to 1.27.0 2022-09-23 15:51:14 +02:00
README.md deps: update osbuild/images to 246b718310ea 2023-07-21 12:05:00 +02:00
retry.go deps: update osbuild/images to 246b718310ea 2023-07-21 12:05:00 +02:00

Internal

This directory contains internal code for cloud.google.com/go packages.

.repo-metadata-full.json

.repo-metadata-full.json contains metadata about the packages in this repo. It is generated by internal/gapicgen/generator. It's processed by external tools to build lists of all of the packages.

Don't make breaking changes to the format without consulting with the external tools.

One day, we may want to create individual .repo-metadata.json files next to each package, which is the pattern followed by some other languages. External tools would then talk to pkg.go.dev or some other service to get the overall list of packages and use the .repo-metadata.json files to get the additional metadata required. For now, .repo-metadata-full.json includes everything.

Updating OwlBot SHA

You may want to manually update the which version of the post-processor will be used -- to do this you need to update the SHA in the OwlBot lock file.

See the postprocessor/README for detailed instructions.

Note: OwlBot will eventually open a pull request to update this value if it discovers a new version of the container.