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!: create V2 release candidates for some components #7577

Merged
merged 18 commits into from
Aug 2, 2024
Merged

Conversation

bshaffer
Copy link
Contributor

@bshaffer bshaffer commented Aug 2, 2024

Creates the V2 release candidate for components with low traffic (e.g. < 1,000 downloads from packagist)

BEGIN_VERSION_OVERRIDE
AccessApproval: 2.0.0-RC1
ApigeeConnect: 2.0.0-RC1
BigQueryReservation: 2.0.0-RC1
BillingBudgets: 2.0.0-RC1
ContactCenterInsights: 2.0.0-RC1
DataCatalog: 2.0.0-RC1
Dms: 2.0.0-RC1
Eventarc: 2.0.0-RC1
Filestore: 2.0.0-RC1
ManagedIdentities: 2.0.0-RC1
NetworkConnectivity: 2.0.0-RC1
NetworkManagement: 2.0.0-RC1
OrchestrationAirflow: 2.0.0-RC1
OsLogin: 2.0.0-RC1
PolicyTroubleshooter: 2.0.0-RC1
Recommender: 2.0.0-RC1
ResourceSettings: 2.0.0-RC1
Shell: 2.0.0-RC1
VpcAccess: 2.0.0-RC1
END_VERSION_OVERRIDE

BREAKING_CHANGE_REASON=removing deprecated surfaces and promoting to v2.0

@bshaffer bshaffer marked this pull request as ready for review August 2, 2024 20:57
@bshaffer bshaffer requested review from a team as code owners August 2, 2024 20:57
@bshaffer bshaffer added the next release PRs to be included in the next release label Aug 2, 2024
@bshaffer bshaffer changed the title feat: create V2 Release candidates for low traffic components chore!: create V2 release candidates for some components Aug 2, 2024
@@ -1,4 +1,4 @@
# Copyright 2021 Google LLC
# Copyright 2023 Google LLC
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be 2024?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm... ideally the copyright wouldn't be updated at all, but the script I wrote does it anyway (it didn't seem worthwhile to go through manually and update them).

It should be 2024 in the template I'm copying from, however. I've made that change here.

@bshaffer bshaffer merged commit aca00f6 into main Aug 2, 2024
30 of 32 checks passed
@bshaffer bshaffer deleted the first-round-v2 branch August 2, 2024 21:33
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