Skip to content

tests: Add java-showcase-3.25.8.#4088

Merged
blakeli0 merged 4 commits intomainfrom
add-showcase-3.25.8
Jan 23, 2026
Merged

tests: Add java-showcase-3.25.8.#4088
blakeli0 merged 4 commits intomainfrom
add-showcase-3.25.8

Conversation

@blakeli0
Copy link
Contributor

Add a new module java-showcase-3.25.8. This is a copy of the java-showcase module with a different version (3.25.8) of protobuf gen code. This is intended to test the compatibility between protobuf runtime v4.33.x and gen code 3.25.8.

Add a new step in CI to test this module.

@product-auto-label product-auto-label bot added the size: xl Pull request size is extra large. label Jan 23, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @blakeli0, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new Java showcase module designed to specifically validate the compatibility between the current protobuf runtime (v4.33.x) and an older version of protobuf generated code (3.25.8). This ensures that client libraries generated with older protobuf versions continue to function correctly with newer runtimes. The changes also integrate this new compatibility test into the existing CI workflow.

Highlights

  • New Module Addition: A new module, java-showcase-3.25.8, has been added to the repository.
  • Protobuf Compatibility Testing: This new module is a copy of the existing java-showcase but uses protobuf generated code version 3.25.8. Its primary purpose is to test compatibility between protobuf runtime v4.33.x and the 3.25.8 generated code.
  • CI Integration: The Continuous Integration (CI) pipeline has been updated to include a new step for testing this recently added module.
  • Generated Code and Configuration: The new module includes its pom.xml configuration, client and settings classes for various services (Compliance, Echo, Identity, Messaging, SequenceService, Testing), GAPIC metadata, and stub implementations for both gRPC and HTTP JSON transports.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/ci.yaml
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@blakeli0 blakeli0 requested a review from JoeWang1127 January 23, 2026 18:06
@sonarqubecloud
Copy link

@sonarqubecloud
Copy link

Quality Gate Passed Quality Gate passed for 'java_showcase_integration_tests'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request introduces a new module, java-showcase-3.25.8, to test compatibility between protobuf-java runtime v4.33.0 and gen code 3.25.8, including a README.md and pom.xml file. The reviewer suggests renaming the artifactId to java-showcase-3.25.8, updating the parent artifactId to java-showcase-3.25.8-parent, renaming the gapic-showcase.version property to something more descriptive like java-showcase.version, clarifying or updating the URL for compliance_suite.json, and explicitly defining the version for protobuf-java.

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.google.cloud</groupId>
<artifactId>gapic-showcase</artifactId>
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The artifactId for this new module should reflect its name, java-showcase-3.25.8, for clarity and consistency with the PR title. Currently, it's gapic-showcase.

Suggested change
<artifactId>gapic-showcase</artifactId>
<artifactId>java-showcase-3.25.8</artifactId>

</description>
<parent>
<groupId>com.google.cloud</groupId>
<artifactId>gapic-showcase-parent</artifactId>
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The artifactId for the parent module should also be updated to reflect the new module's naming convention, e.g., java-showcase-3.25.8-parent or a more generic parent if applicable. Currently, it's gapic-showcase-parent.

Suggested change
<artifactId>gapic-showcase-parent</artifactId>
<artifactId>java-showcase-3.25.8-parent</artifactId>

</parent>

<properties>
<gapic-showcase.version>0.36.2</gapic-showcase.version>
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The property name gapic-showcase.version might be misleading since this is a new module named java-showcase-3.25.8. Consider renaming it to something more descriptive like java-showcase.version or protobuf-gen-code.version to accurately reflect its purpose.

Suggested change
<gapic-showcase.version>0.36.2</gapic-showcase.version>
<java-showcase.version>0.36.2</java-showcase.version>

</goals>
<configuration>
<url>
https://raw.githubusercontent.com/googleapis/gapic-showcase/v${gapic-showcase.version}/server/services/compliance_suite.json
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The URL for compliance_suite.json uses ${gapic-showcase.version}. If gapic-showcase.version refers to the original gapic-showcase module's version, this might be correct. However, if this new module has its own versioning for the compliance suite, this should be updated to use a relevant property (e.g., the one suggested in the previous comment). Please clarify or update this reference.

Suggested change
https://raw.githubusercontent.com/googleapis/gapic-showcase/v${gapic-showcase.version}/server/services/compliance_suite.json
https://raw.githubusercontent.com/googleapis/gapic-showcase/v${java-showcase.version}/server/services/compliance_suite.json

</dependency>
<dependency>
<groupId>com.google.protobuf</groupId>
<artifactId>protobuf-java</artifactId>
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

It's good practice to explicitly define the version for protobuf-java to ensure build reproducibility and avoid potential conflicts with other dependencies. Please add a <version> tag here.

      <artifactId>protobuf-java</artifactId>
      <version>3.25.8</version>

@blakeli0 blakeli0 merged commit 9cf0352 into main Jan 23, 2026
58 of 61 checks passed
@blakeli0 blakeli0 deleted the add-showcase-3.25.8 branch January 23, 2026 19:49
lqiu96 pushed a commit that referenced this pull request Feb 12, 2026
Add a new module java-showcase-3.25.8. This is a copy of the
java-showcase module with a different version (3.25.8) of protobuf gen
code. This is intended to test the compatibility between protobuf
runtime v4.33.x and gen code 3.25.8.

Add [a new step](https://github.com/googleapis/sdk-platform-java/blob/bccc9ded96f5313c22cd4543c25e49fb673792f6/.github/workflows/ci.yaml#L306-L312)
in CI to test this module.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size: xl Pull request size is extra large.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants