debian-forge-composer/vendor/cloud.google.com/go/internal
Michael Vogt 409b4f6048 go.mod: update to images@v0.117.0
This commit updates to images v0.117.0 so that the cross-distro.sh
test works again (images removed fedora-39.json in main but the
uses the previous version of images that includes fedora-39 so
there is a mismatch (we should look into if there is a way to
get github.com/osbuild/images@latest instead of main in the
cross-arch test).

It also updates all the vendor stuff that got pulled via the
new images release (which is giantonormous).

This update requires updating the Go version to 1.22.8
2025-02-19 19:19:42 +01:00
..
optional internal/upload: Add support for upload to GCP and CLI tool using it 2021-02-25 18:44:21 +00:00
trace go.mod: update to images@v0.117.0 2025-02-19 19:19:42 +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: update to images@v0.117.0 2025-02-19 19:19:42 +01: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
gen_info.sh go.mod: update osbuild/images to v0.69.0 2024-07-04 19:01:07 +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.