particle-os/debian-forge-composer
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
debian-forge-composer/vendor/cloud.google.com/go/internal
History
dependabot[bot] 49cf427e6a build(deps): bump cloud.google.com/go/storage from 1.26.0 to 1.27.0 
Bumps [cloud.google.com/go/storage](https://github.com/googleapis/google-cloud-go) from 1.26.0 to 1.27.0.
- [Release notes](https://github.com/googleapis/google-cloud-go/releases)
- [Changelog](https://github.com/googleapis/google-cloud-go/blob/main/CHANGES.md)
- [Commits](https://github.com/googleapis/google-cloud-go/compare/spanner/v1.26.0...spanner/v1.27.0)

---
updated-dependencies:
- dependency-name: cloud.google.com/go/storage
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2022-09-23 15:51:14 +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 build(deps): bump cloud.google.com/go/storage from 1.26.0 to 1.27.0 2022-09-23 15:51:14 +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 internal/upload: Add support for upload to GCP and CLI tool using it 2021-02-25 18:44:21 +00:00
retry.go build(deps): bump cloud.google.com/go/storage from 1.16.1 to 1.18.1 2021-10-18 07:54:09 +01:00

README.md

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.