Skip to content

feat(apigee_registry)!: replace apigee registry gems with tombstones - #36233

Open
torreypayne wants to merge 1 commit into
mainfrom
tombstone-apigee-registry
Open

feat(apigee_registry)!: replace apigee registry gems with tombstones#36233
torreypayne wants to merge 1 commit into
mainfrom
tombstone-apigee-registry

Conversation

@torreypayne

@torreypayne torreypayne commented Aug 11, 2026

Copy link
Copy Markdown
Member

Replaces google-cloud-apigee_registry (wrapper gem) and google-cloud-apigee_registry-v1 (versioned client gem) with minimal tombstone packages.

Details of Changes

  • Tooling Pre-requisites & Upstream Fixes: Generated via toys tombstone-library incorporating upstream fixes from:
  • Skeleton Replacement: Purges functional source code and runtime dependencies, replacing them with minimal tombstone skeletons (version constants, README, LICENSE, .yardopts, Rakefile).
  • Release Please: Merging with feat!: conventional commit breaking change prefix will automatically trigger Release Please to bump both packages to their next major versions (google-cloud-apigee_registry 2.0.0 and google-cloud-apigee_registry-v1 1.0.0) and generate the release PR.

Fixes: b/545644248

@aandreassa

Copy link
Copy Markdown
Contributor

@torreypayne I get what you are trying to do, but BEGIN_COMMIT_OVERRIDE block won't work since it has two Release-As entries. I recommend just removing it and using after the fact if you still need it.

Merging as feat! should be enough to bump them individually! (to their next major versions, 2.0.0 and 1.0.0)

Comment thread google-cloud-apigee_registry-v1/lib/google/cloud/apigee_registry/v1/version.rb Outdated
@torreypayne
torreypayne force-pushed the tombstone-apigee-registry branch from cb3ca51 to 3a2e266 Compare August 12, 2026 21:44
@torreypayne torreypayne changed the title feat(apigee_registry)!: replace apigee registry gems with tombstones feat(google-cloud-apigee_registry)!: replace gem with tombstone Aug 12, 2026
@aandreassa

Copy link
Copy Markdown
Contributor

@torreypayne looks like you can't separate them since there is a dependency of wrapper & versioned. Not splitting it is fine since the commit message is OK to used across for bumping.

@torreypayne
torreypayne force-pushed the tombstone-apigee-registry branch from 3a2e266 to 18c5f06 Compare August 12, 2026 22:00
@torreypayne torreypayne changed the title feat(google-cloud-apigee_registry)!: replace gem with tombstone feat(apigee_registry)!: replace apigee registry gems with tombstones Aug 12, 2026
@aandreassa

Copy link
Copy Markdown
Contributor

LGTM. Please make sure to merge googleapis/ruby-common-tools#454 if it still needed.

Comment thread google-cloud-apigee_registry-v1/lib/google/cloud/apigee_registry/v1/version.rb Outdated
@torreypayne
torreypayne force-pushed the tombstone-apigee-registry branch 2 times, most recently from 7aa4233 to e6b6d69 Compare August 12, 2026 22:12
@torreypayne
torreypayne force-pushed the tombstone-apigee-registry branch from e6b6d69 to 0acb09e Compare August 12, 2026 22:18
@torreypayne
torreypayne marked this pull request as ready for review August 12, 2026 22:34
@torreypayne
torreypayne requested review from a team and yoshi-approver as code owners August 12, 2026 22:34
@snippet-bot

snippet-bot Bot commented Aug 12, 2026

Copy link
Copy Markdown

Here is the summary of changes.

You are about to delete 38 region tags.

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

  • Refresh this comment

@torreypayne
torreypayne requested a review from aandreassa August 12, 2026 23:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants