fix(internal/gapicgen): properly update modules that have no gapic changes (#5945)

Previously this was happening thanks to some logic the revolved around
looking for UNKNOWN date in a generated gapic client. This logic was
removed around a month ago and hense PRs that have genproto changes
but no gapic changes have needed some manual updates. With this change
the update process now parses out what kind of changes happened based
on context aware commit messages. This means even if there we not chnages
to the gapic client genproto will still get updated to the latest version
if there were changes to message types.
3 files changed
tree: a602e816c9166a3b94d9d7416ca3a01fb19f7993
  1. .github/
  2. accessapproval/
  3. accesscontextmanager/
  4. aiplatform/
  5. analytics/
  6. apigateway/
  7. apigeeconnect/
  8. appengine/
  9. area120/
  10. artifactregistry/
  11. asset/
  12. assuredworkloads/
  13. automl/
  14. bigquery/
  15. bigtable/
  16. billing/
  17. binaryauthorization/
  18. certificatemanager/
  19. channel/
  20. civil/
  21. cloudbuild/
  22. clouddms/
  23. cloudtasks/
  24. cmd/
  25. compute/
  26. contactcenterinsights/
  27. container/
  28. containeranalysis/
  29. datacatalog/
  30. dataflow/
  31. datafusion/
  32. datalabeling/
  33. dataplex/
  34. dataproc/
  35. dataqna/
  36. datastore/
  37. datastream/
  38. debugger/
  39. deploy/
  40. dialogflow/
  41. dlp/
  42. documentai/
  43. domains/
  44. errorreporting/
  45. essentialcontacts/
  46. eventarc/
  47. filestore/
  48. firestore/
  49. functions/
  50. gaming/
  51. gkeconnect/
  52. gkehub/
  53. grafeas/
  54. gsuiteaddons/
  55. httpreplay/
  56. iam/
  57. iap/
  58. ids/
  59. internal/
  60. iot/
  61. kms/
  62. language/
  63. lifesciences/
  64. logging/
  65. longrunning/
  66. managedidentities/
  67. mediatranslation/
  68. memcache/
  69. metastore/
  70. monitoring/
  71. networkconnectivity/
  72. networkmanagement/
  73. networksecurity/
  74. notebooks/
  75. optimization/
  76. orchestration/
  77. orgpolicy/
  78. osconfig/
  79. oslogin/
  80. phishingprotection/
  81. policytroubleshooter/
  82. privatecatalog/
  83. profiler/
  84. pubsub/
  85. pubsublite/
  86. recaptchaenterprise/
  87. recommendationengine/
  88. recommender/
  89. redis/
  90. resourcemanager/
  91. resourcesettings/
  92. retail/
  93. rpcreplay/
  94. run/
  95. scheduler/
  96. secretmanager/
  97. security/
  98. securitycenter/
  99. servicecontrol/
  100. servicedirectory/
  101. servicemanagement/
  102. serviceusage/
  103. shell/
  104. spanner/
  105. speech/
  106. storage/
  107. storagetransfer/
  108. talent/
  109. texttospeech/
  110. third_party/
  111. tpu/
  112. trace/
  113. translate/
  114. video/
  115. videointelligence/
  116. vision/
  117. vmmigration/
  118. vpcaccess/
  119. webrisk/
  120. websecurityscanner/
  121. workflows/
  122. .gitignore
  123. .release-please-manifest-submodules.json
  124. .release-please-manifest.json
  125. CHANGES.md
  126. CODE_OF_CONDUCT.md
  127. CONTRIBUTING.md
  128. doc.go
  129. go.mod
  130. go.sum
  131. header_test.go
  132. LICENSE
  133. README.md
  134. release-please-config-yoshi-submodules.json
  135. release-please-config.json
  136. RELEASING.md
  137. SECURITY.md
  138. testing.md
README.md

Google Cloud Client Libraries for Go

Go Reference

Go packages for Google Cloud Platform services.

import "cloud.google.com/go"

To install the packages on your system, do not clone the repo. Instead:

  1. Change to your project directory:

    cd /my/cloud/project
    
  2. Get the package you want to use. Some products have their own module, so it's best to go get the package(s) you want to use:

    $ go get cloud.google.com/go/firestore # Replace with the package you want to use.
    

NOTE: Some of these packages are under development, and may occasionally make backwards-incompatible changes.

Supported APIs

For an updated list of all of our released APIs please see our reference docs.

Go Versions Supported

Our libraries are compatible with at least the three most recent, major Go releases. They are currently compatible with:

  • Go 1.18
  • Go 1.17
  • Go 1.16
  • Go 1.15

Authorization

By default, each API will use Google Application Default Credentials for authorization credentials used in calling the API endpoints. This will allow your application to run in many environments without requiring explicit configuration.

client, err := storage.NewClient(ctx)

To authorize using a JSON key file, pass option.WithCredentialsFile to the NewClient function of the desired package. For example:

client, err := storage.NewClient(ctx, option.WithCredentialsFile("path/to/keyfile.json"))

You can exert more control over authorization by using the golang.org/x/oauth2 package to create an oauth2.TokenSource. Then pass option.WithTokenSource to the NewClient function: snip:# (auth-ts)

tokenSource := ...
client, err := storage.NewClient(ctx, option.WithTokenSource(tokenSource))

Contributing

Contributions are welcome. Please, see the CONTRIBUTING document for details.

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms. See Contributor Code of Conduct for more information.

Links