Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore!: promote CertificateManager, ContainerAnalysis, ConfidentialComputing, DataCatalogLineage, GkeBackup, Grafeas, ResourceManager to v1 #7464

Merged
merged 7 commits into from
Jun 28, 2024

Conversation

bshaffer
Copy link
Contributor

@bshaffer bshaffer commented Jun 24, 2024

promote the following components to v1 and mark as stable:

  • CertificateManager
  • ContainerAnalysis
  • ConfidentialComputing
  • DataCatalogLineage
  • GkeBackup
  • Grafeas
  • ResourceManager

see cl/646200778

BREAKING_CHANGE_REASON=major version bump

BEGIN_VERSION_OVERRIDE
CertificateManager: 1.0.0-RC1
ContainerAnalysis: 1.0.0
ConfidentialComputing: 1.0.0
DataCatalogLineage: 1.0.0
GkeBackup: 1.0.0
Grafeas: 1.0.0-RC1
ResourceManager: 1.0.0
END_VERSION_OVERRIDE

@bshaffer bshaffer force-pushed the promote-v1-batch3 branch from 3aa67b4 to 559a054 Compare June 24, 2024 20:32
@bshaffer bshaffer changed the title promote v1 batch3 chore!: promote CertificateManager, ContainerAnalysis, ConfidentialComputing, DataCatalogLineage, GkeBackup, Grafeas, ResourceManager to v1 Jun 24, 2024
@bshaffer bshaffer marked this pull request as ready for review June 25, 2024 13:28
@bshaffer bshaffer requested review from a team as code owners June 25, 2024 13:28
@bshaffer bshaffer added the next release PRs to be included in the next release label Jun 25, 2024
@bshaffer bshaffer merged commit c5cf0eb into main Jun 28, 2024
29 checks passed
@bshaffer bshaffer deleted the promote-v1-batch3 branch June 28, 2024 21:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
next release PRs to be included in the next release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants