Skip to content

feat(google-cloud-apigee_registry-v1)!: replace gem with tombstone - #36242

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

feat(google-cloud-apigee_registry-v1)!: replace gem with tombstone#36242
torreypayne wants to merge 1 commit into
mainfrom
tombstone-apigee-registry-v1

Conversation

@torreypayne

Copy link
Copy Markdown
Member

Replaces google-cloud-apigee_registry-v1 with a minimal tombstone package.

Details of Changes

  • Generated via toys tombstone-library using updated templates from googleapis/ruby-common-tools#453 and googleapis/ruby-common-tools#455.
  • Replaces functional code with minimal tombstone skeleton (version constant, README, LICENSE, .yardopts).
  • Includes minimal Rakefile with require "bundler/gem_tasks" to ensure automated release builds (rake build) succeed out of the box during CI/CD packaging.
  • Removes all runtime dependencies and functional code.
  • Merging with feat!: conventional commit breaking change prefix will bump the package to its next major version: 1.0.0.

Fixes: b/545644248

@torreypayne

Copy link
Copy Markdown
Member Author

Closing in favor of consolidating both gems into #36233.

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.

1 participant