diff --git a/.cloudbuild/graalvm/cloudbuild-test-a.yaml b/.cloudbuild/graalvm/cloudbuild-test-a.yaml index 030f2a6e00..397564e516 100644 --- a/.cloudbuild/graalvm/cloudbuild-test-a.yaml +++ b/.cloudbuild/graalvm/cloudbuild-test-a.yaml @@ -14,7 +14,7 @@ timeout: 7200s # 2 hours substitutions: - _SHARED_DEPENDENCIES_VERSION: '3.52.0' # {x-version-update:google-cloud-shared-dependencies:current} + _SHARED_DEPENDENCIES_VERSION: '3.52.1' # {x-version-update:google-cloud-shared-dependencies:current} _JAVA_SHARED_CONFIG_VERSION: '1.16.1' options: machineType: 'E2_HIGHCPU_8' diff --git a/.cloudbuild/graalvm/cloudbuild-test-b.yaml b/.cloudbuild/graalvm/cloudbuild-test-b.yaml index 911045b3ca..b29604305e 100644 --- a/.cloudbuild/graalvm/cloudbuild-test-b.yaml +++ b/.cloudbuild/graalvm/cloudbuild-test-b.yaml @@ -14,7 +14,7 @@ timeout: 7200s # 2 hours substitutions: - _SHARED_DEPENDENCIES_VERSION: '3.52.0' # {x-version-update:google-cloud-shared-dependencies:current} + _SHARED_DEPENDENCIES_VERSION: '3.52.1' # {x-version-update:google-cloud-shared-dependencies:current} _JAVA_SHARED_CONFIG_VERSION: '1.16.1' options: machineType: 'E2_HIGHCPU_8' diff --git a/.cloudbuild/graalvm/cloudbuild-test-c.yaml b/.cloudbuild/graalvm/cloudbuild-test-c.yaml index e60c6ececa..06d79a6c51 100644 --- a/.cloudbuild/graalvm/cloudbuild-test-c.yaml +++ b/.cloudbuild/graalvm/cloudbuild-test-c.yaml @@ -14,7 +14,7 @@ timeout: 7200s # 2 hours substitutions: - _SHARED_DEPENDENCIES_VERSION: '3.52.0' # {x-version-update:google-cloud-shared-dependencies:current} + _SHARED_DEPENDENCIES_VERSION: '3.52.1' # {x-version-update:google-cloud-shared-dependencies:current} _JAVA_SHARED_CONFIG_VERSION: '1.16.1' options: machineType: 'E2_HIGHCPU_8' diff --git a/.cloudbuild/graalvm/cloudbuild.yaml b/.cloudbuild/graalvm/cloudbuild.yaml index ce48e5b047..a52e356033 100644 --- a/.cloudbuild/graalvm/cloudbuild.yaml +++ b/.cloudbuild/graalvm/cloudbuild.yaml @@ -14,7 +14,7 @@ timeout: 7200s # 2 hours substitutions: - _SHARED_DEPENDENCIES_VERSION: '3.52.0' # {x-version-update:google-cloud-shared-dependencies:current} + _SHARED_DEPENDENCIES_VERSION: '3.52.1' # {x-version-update:google-cloud-shared-dependencies:current} _JAVA_SHARED_CONFIG_VERSION: '1.16.1' steps: # GraalVM A build diff --git a/.cloudbuild/library_generation/cloudbuild-library-generation-push.yaml b/.cloudbuild/library_generation/cloudbuild-library-generation-push.yaml index ed949d8cfd..5a427abe87 100644 --- a/.cloudbuild/library_generation/cloudbuild-library-generation-push.yaml +++ b/.cloudbuild/library_generation/cloudbuild-library-generation-push.yaml @@ -14,7 +14,7 @@ timeout: 7200s # 2 hours substitutions: - _GAPIC_GENERATOR_JAVA_VERSION: '2.62.0' # {x-version-update:gapic-generator-java:current} + _GAPIC_GENERATOR_JAVA_VERSION: '2.62.1' # {x-version-update:gapic-generator-java:current} _PRIVATE_IMAGE_NAME: "us-docker.pkg.dev/java-hermetic-build-prod/private-resources/java-library-generation" _PRIVATE_SHA_IMAGE_ID: "${_PRIVATE_IMAGE_NAME}:${COMMIT_SHA}" _PRIVATE_LATEST_IMAGE_ID: "${_PRIVATE_IMAGE_NAME}:latest" diff --git a/.cloudbuild/library_generation/library_generation.Dockerfile b/.cloudbuild/library_generation/library_generation.Dockerfile index bcbc886704..db98f1dfd1 100644 --- a/.cloudbuild/library_generation/library_generation.Dockerfile +++ b/.cloudbuild/library_generation/library_generation.Dockerfile @@ -21,7 +21,7 @@ FROM docker.io/library/maven:3.9.9-eclipse-temurin-17-alpine@sha256:969014ee8852 WORKDIR /sdk-platform-java COPY . . # {x-version-update-start:gapic-generator-java:current} -ENV DOCKER_GAPIC_GENERATOR_VERSION="2.62.0" +ENV DOCKER_GAPIC_GENERATOR_VERSION="2.62.1" # {x-version-update-end} # Download the java formatter diff --git a/.cloudbuild/library_generation/library_generation_airlock.Dockerfile b/.cloudbuild/library_generation/library_generation_airlock.Dockerfile index d3efbc156c..61aba1a029 100644 --- a/.cloudbuild/library_generation/library_generation_airlock.Dockerfile +++ b/.cloudbuild/library_generation/library_generation_airlock.Dockerfile @@ -21,7 +21,7 @@ FROM us-docker.pkg.dev/artifact-foundry-prod/docker-3p-trusted/maven@sha256:d3f0 WORKDIR /sdk-platform-java COPY . . # {x-version-update-start:gapic-generator-java:current} -ENV DOCKER_GAPIC_GENERATOR_VERSION="2.62.0" +ENV DOCKER_GAPIC_GENERATOR_VERSION="2.62.1" # {x-version-update-end} # Download the java formatter diff --git a/.github/workflows/gemini-cli.yml b/.github/workflows/gemini-cli.yml index a3cecf0f1f..9257b7b2b2 100644 --- a/.github/workflows/gemini-cli.yml +++ b/.github/workflows/gemini-cli.yml @@ -1,270 +1,270 @@ -name: '💬 Gemini CLI' - -on: - issue_comment: - types: [created] - -concurrency: - group: '${{ github.workflow }}-${{ github.event.issue.number }}' - cancel-in-progress: |- - ${{ github.event.sender.type == 'User' && ( github.event.issue.author_association == 'OWNER' || github.event.issue.author_association == 'MEMBER' || github.event.issue.author_association == 'COLLABORATOR') }} - -defaults: - run: - shell: 'bash' - -permissions: - contents: 'write' - id-token: 'write' - pull-requests: 'write' - issues: 'write' - -jobs: - gemini-cli: - # This condition is complex to ensure we only run when explicitly invoked. - if: |- - github.event_name == 'workflow_dispatch' || - ( - github.event_name == 'issues' && github.event.action == 'opened' && - contains(github.event.issue.body, '@gemini-cli') && - !contains(github.event.issue.body, '@gemini-cli /review') && - !contains(github.event.issue.body, '@gemini-cli /triage') && - contains(fromJSON('["OWNER", "MEMBER", "COLLABORATOR"]'), github.event.issue.author_association) - ) || - ( - github.event_name == 'issue_comment' && - contains(github.event.comment.body, '@gemini-cli') && - !contains(github.event.comment.body, '@gemini-cli /review') && - !contains(github.event.comment.body, '@gemini-cli /triage') && - contains(fromJSON('["OWNER", "MEMBER", "COLLABORATOR"]'), github.event.comment.author_association) - ) - timeout-minutes: 10 - runs-on: 'ubuntu-latest' - - steps: - - name: 'Get context from event' - id: 'get_context' - env: - EVENT_NAME: '${{ github.event_name }}' - EVENT_PAYLOAD: '${{ toJSON(github.event) }}' - run: |- - set -euo pipefail - - USER_REQUEST="" - ISSUE_NUMBER="" - IS_PR="false" - - if [[ "${EVENT_NAME}" == "issues" ]]; then - USER_REQUEST=$(echo "${EVENT_PAYLOAD}" | jq -r .issue.body) - ISSUE_NUMBER=$(echo "${EVENT_PAYLOAD}" | jq -r .issue.number) - elif [[ "${EVENT_NAME}" == "issue_comment" ]]; then - USER_REQUEST=$(echo "${EVENT_PAYLOAD}" | jq -r .comment.body) - ISSUE_NUMBER=$(echo "${EVENT_PAYLOAD}" | jq -r .issue.number) - if [[ $(echo "${EVENT_PAYLOAD}" | jq -r .issue.pull_request) != "null" ]]; then - IS_PR="true" - fi - fi - - # Clean up user request - USER_REQUEST=$(echo "${USER_REQUEST}" | sed 's/.*@gemini-cli//' | sed 's/^[[:space:]]*//;s/[[:space:]]*$//') - - { - echo "user_request=${USER_REQUEST}" - echo "issue_number=${ISSUE_NUMBER}" - echo "is_pr=${IS_PR}" - } >> "${GITHUB_OUTPUT}" - - - name: 'Set up git user for commits' - run: |- - git config --global user.name 'gemini-cli[bot]' - git config --global user.email 'gemini-cli[bot]@users.noreply.github.com' - - - name: 'Checkout PR branch' - if: |- - ${{ steps.get_context.outputs.is_pr == 'true' }} - uses: 'actions/checkout@v5' - with: - token: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' - repository: '${{ github.repository }}' - ref: 'refs/pull/${{ steps.get_context.outputs.issue_number }}/head' - fetch-depth: 0 - - - name: 'Checkout main branch' - if: |- - ${{ steps.get_context.outputs.is_pr == 'false' }} - uses: 'actions/checkout@v5' - with: - token: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' - repository: '${{ github.repository }}' - fetch-depth: 0 - - - name: 'Acknowledge request' - env: - GITHUB_ACTOR: '${{ github.actor }}' - GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' - ISSUE_NUMBER: '${{ steps.get_context.outputs.issue_number }}' - REPOSITORY: '${{ github.repository }}' - REQUEST_TYPE: '${{ steps.get_context.outputs.request_type }}' - run: |- - set -euo pipefail - MESSAGE="@${GITHUB_ACTOR} I've received your request and I'm working on it now! 🤖" - if [[ -n "${MESSAGE}" ]]; then - gh issue comment "${ISSUE_NUMBER}" \ - --body "${MESSAGE}" \ - --repo "${REPOSITORY}" - fi - - - name: 'Get description' - id: 'get_description' - env: - GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' - IS_PR: '${{ steps.get_context.outputs.is_pr }}' - ISSUE_NUMBER: '${{ steps.get_context.outputs.issue_number }}' - run: |- - set -euo pipefail - if [[ "${IS_PR}" == "true" ]]; then - DESCRIPTION=$(gh pr view "${ISSUE_NUMBER}" --json body --template '{{.body}}') - else - DESCRIPTION=$(gh issue view "${ISSUE_NUMBER}" --json body --template '{{.body}}') - fi - { - echo "description<> "${GITHUB_OUTPUT}" - - - name: 'Get comments' - id: 'get_comments' - env: - GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' - IS_PR: '${{ steps.get_context.outputs.is_pr }}' - ISSUE_NUMBER: '${{ steps.get_context.outputs.issue_number }}' - run: |- - set -euo pipefail - if [[ "${IS_PR}" == "true" ]]; then - COMMENTS=$(gh pr view "${ISSUE_NUMBER}" --json comments --template '{{range .comments}}{{.author.login}}: {{.body}}{{"\n"}}{{end}}') - else - COMMENTS=$(gh issue view "${ISSUE_NUMBER}" --json comments --template '{{range .comments}}{{.author.login}}: {{.body}}{{"\n"}}{{end}}') - fi - { - echo "comments<> "${GITHUB_OUTPUT}" - - - name: 'Run Gemini' - id: 'run_gemini' - uses: 'google-github-actions/run-gemini-cli@v0' - env: - GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' - REPOSITORY: '${{ github.repository }}' - USER_REQUEST: '${{ steps.get_context.outputs.user_request }}' - ISSUE_NUMBER: '${{ steps.get_context.outputs.issue_number }}' - IS_PR: '${{ steps.get_context.outputs.is_pr }}' - with: - gemini_api_key: '${{ secrets.GEMINI_API_KEY }}' - gcp_workload_identity_provider: '${{ vars.GCP_WIF_PROVIDER }}' - gcp_project_id: '${{ vars.GOOGLE_CLOUD_PROJECT }}' - gcp_location: '${{ vars.GOOGLE_CLOUD_LOCATION }}' - gcp_service_account: '${{ vars.SERVICE_ACCOUNT_EMAIL }}' - use_vertex_ai: '${{ vars.GOOGLE_GENAI_USE_VERTEXAI }}' - use_gemini_code_assist: '${{ vars.GOOGLE_GENAI_USE_GCA }}' - settings: |- - { - "maxSessionTurns": 50, - "telemetry": { - "enabled": false, - "target": "gcp" - } - } - prompt: |- - ## Role - - You are a helpful AI assistant invoked via a CLI interface in a GitHub workflow. You have access to tools to interact with the repository and respond to the user. - - ## Context - - - **Repository**: `${{ github.repository }}` - - **Triggering Event**: `${{ github.event_name }}` - - **Issue/PR Number**: `${{ steps.get_context.outputs.issue_number }}` - - **Is this a PR?**: `${{ steps.get_context.outputs.is_pr }}` - - **Issue/PR Description**: - `${{ steps.get_description.outputs.description }}` - - **Comments**: - `${{ steps.get_comments.outputs.comments }}` - - ## User Request - - The user has sent the following request: - `${{ steps.get_context.outputs.user_request }}` - - ## How to Respond to Issues, PR Comments, and Questions - - This workflow supports three main scenarios: - - 1. **Creating a Fix for an Issue** - - Carefully read the user request and the related issue or PR description. - - Use available tools to gather all relevant context (e.g., `gh issue view`, `gh pr view`, `gh pr diff`, `cat`, `head`, `tail`). - - Identify the root cause of the problem before proceeding. - - **Show and maintain a plan as a checklist**: - - At the very beginning, outline the steps needed to resolve the issue or address the request and post them as a checklist comment on the issue or PR (use GitHub markdown checkboxes: `- [ ] Task`). - - Example: - ``` - ### Plan - - [ ] Investigate the root cause - - [ ] Implement the fix in `file.py` - - [ ] Add/modify tests - - [ ] Update documentation - - [ ] Verify the fix and close the issue - ``` - - Use: `gh pr comment "${ISSUE_NUMBER}" --body ""` or `gh issue comment "${ISSUE_NUMBER}" --body ""` to post the initial plan. - - As you make progress, keep the checklist visible and up to date by editing the same comment (check off completed tasks with `- [x]`). - - To update the checklist: - 1. Find the comment ID for the checklist (use `gh pr comment list "${ISSUE_NUMBER}"` or `gh issue comment list "${ISSUE_NUMBER}"`). - 2. Edit the comment with the updated checklist: - - For PRs: `gh pr comment --edit --body ""` - - For Issues: `gh issue comment --edit --body ""` - 3. The checklist should only be maintained as a comment on the issue or PR. Do not track or update the checklist in code files. - - If the fix requires code changes, determine which files and lines are affected. If clarification is needed, note any questions for the user. - - Make the necessary code or documentation changes using the available tools (e.g., `write_file`). Ensure all changes follow project conventions and best practices. Reference all shell variables as `"${VAR}"` (with quotes and braces) to prevent errors. - - Run any relevant tests or checks to verify the fix works as intended. If possible, provide evidence (test output, screenshots, etc.) that the issue is resolved. - - **Branching and Committing**: - - **NEVER commit directly to the `main` branch.** - - If you are working on a **pull request** (`IS_PR` is `true`), the correct branch is already checked out. Simply commit and push to it. - - `git add .` - - `git commit -m "feat: "` - - `git push` - - If you are working on an **issue** (`IS_PR` is `false`), create a new branch for your changes. A good branch name would be `issue/${ISSUE_NUMBER}/`. - - `git checkout -b issue/${ISSUE_NUMBER}/my-fix` - - `git add .` - - `git commit -m "feat: "` - - `git push origin issue/${ISSUE_NUMBER}/my-fix` - - After pushing, you can create a pull request: `gh pr create --title "Fixes #${ISSUE_NUMBER}: " --body "This PR addresses issue #${ISSUE_NUMBER}."` - - Summarize what was changed and why in a markdown file: `write_file("response.md", "")` - - Post the response as a comment: - - For PRs: `gh pr comment "${ISSUE_NUMBER}" --body-file response.md` - - For Issues: `gh issue comment "${ISSUE_NUMBER}" --body-file response.md` - - 2. **Addressing Comments on a Pull Request** - - Read the specific comment and the context of the PR. - - Use tools like `gh pr view`, `gh pr diff`, and `cat` to understand the code and discussion. - - If the comment requests a change or clarification, follow the same process as for fixing an issue: create a checklist plan, implement, test, and commit any required changes, updating the checklist as you go. - - **Committing Changes**: The correct PR branch is already checked out. Simply add, commit, and push your changes. - - `git add .` - - `git commit -m "fix: address review comments"` - - `git push` - - If the comment is a question, answer it directly and clearly, referencing code or documentation as needed. - - Document your response in `response.md` and post it as a PR comment: `gh pr comment "${ISSUE_NUMBER}" --body-file response.md` - - 3. **Answering Any Question on an Issue** - - Read the question and the full issue context using `gh issue view` and related tools. - - Research or analyze the codebase as needed to provide an accurate answer. - - If the question requires code or documentation changes, follow the fix process above, including creating and updating a checklist plan and **creating a new branch for your changes as described in section 1.** - - Write a clear, concise answer in `response.md` and post it as an issue comment: `gh issue comment "${ISSUE_NUMBER}" --body-file response.md` - - ## Guidelines - - - **Be concise and actionable.** Focus on solving the user's problem efficiently. - - **Always commit and push your changes if you modify code or documentation.** - - **If you are unsure about the fix or answer, explain your reasoning and ask clarifying questions.** - - **Follow project conventions and best practices.** +#name: '💬 Gemini CLI' +# +#on: +# issue_comment: +# types: [created] +# +#concurrency: +# group: '${{ github.workflow }}-${{ github.event.issue.number }}' +# cancel-in-progress: |- +# ${{ github.event.sender.type == 'User' && ( github.event.issue.author_association == 'OWNER' || github.event.issue.author_association == 'MEMBER' || github.event.issue.author_association == 'COLLABORATOR') }} +# +#defaults: +# run: +# shell: 'bash' +# +#permissions: +# contents: 'write' +# id-token: 'write' +# pull-requests: 'write' +# issues: 'write' +# +#jobs: +# gemini-cli: +# # This condition is complex to ensure we only run when explicitly invoked. +# if: |- +# github.event_name == 'workflow_dispatch' || +# ( +# github.event_name == 'issues' && github.event.action == 'opened' && +# contains(github.event.issue.body, '@gemini-cli') && +# !contains(github.event.issue.body, '@gemini-cli /review') && +# !contains(github.event.issue.body, '@gemini-cli /triage') && +# contains(fromJSON('["OWNER", "MEMBER", "COLLABORATOR"]'), github.event.issue.author_association) +# ) || +# ( +# github.event_name == 'issue_comment' && +# contains(github.event.comment.body, '@gemini-cli') && +# !contains(github.event.comment.body, '@gemini-cli /review') && +# !contains(github.event.comment.body, '@gemini-cli /triage') && +# contains(fromJSON('["OWNER", "MEMBER", "COLLABORATOR"]'), github.event.comment.author_association) +# ) +# timeout-minutes: 10 +# runs-on: 'ubuntu-latest' +# +# steps: +# - name: 'Get context from event' +# id: 'get_context' +# env: +# EVENT_NAME: '${{ github.event_name }}' +# EVENT_PAYLOAD: '${{ toJSON(github.event) }}' +# run: |- +# set -euo pipefail +# +# USER_REQUEST="" +# ISSUE_NUMBER="" +# IS_PR="false" +# +# if [[ "${EVENT_NAME}" == "issues" ]]; then +# USER_REQUEST=$(echo "${EVENT_PAYLOAD}" | jq -r .issue.body) +# ISSUE_NUMBER=$(echo "${EVENT_PAYLOAD}" | jq -r .issue.number) +# elif [[ "${EVENT_NAME}" == "issue_comment" ]]; then +# USER_REQUEST=$(echo "${EVENT_PAYLOAD}" | jq -r .comment.body) +# ISSUE_NUMBER=$(echo "${EVENT_PAYLOAD}" | jq -r .issue.number) +# if [[ $(echo "${EVENT_PAYLOAD}" | jq -r .issue.pull_request) != "null" ]]; then +# IS_PR="true" +# fi +# fi +# +# # Clean up user request +# USER_REQUEST=$(echo "${USER_REQUEST}" | sed 's/.*@gemini-cli//' | sed 's/^[[:space:]]*//;s/[[:space:]]*$//') +# +# { +# echo "user_request=${USER_REQUEST}" +# echo "issue_number=${ISSUE_NUMBER}" +# echo "is_pr=${IS_PR}" +# } >> "${GITHUB_OUTPUT}" +# +# - name: 'Set up git user for commits' +# run: |- +# git config --global user.name 'gemini-cli[bot]' +# git config --global user.email 'gemini-cli[bot]@users.noreply.github.com' +# +# - name: 'Checkout PR branch' +# if: |- +# ${{ steps.get_context.outputs.is_pr == 'true' }} +# uses: 'actions/checkout@v5' +# with: +# token: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' +# repository: '${{ github.repository }}' +# ref: 'refs/pull/${{ steps.get_context.outputs.issue_number }}/head' +# fetch-depth: 0 +# +# - name: 'Checkout main branch' +# if: |- +# ${{ steps.get_context.outputs.is_pr == 'false' }} +# uses: 'actions/checkout@v5' +# with: +# token: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' +# repository: '${{ github.repository }}' +# fetch-depth: 0 +# +# - name: 'Acknowledge request' +# env: +# GITHUB_ACTOR: '${{ github.actor }}' +# GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' +# ISSUE_NUMBER: '${{ steps.get_context.outputs.issue_number }}' +# REPOSITORY: '${{ github.repository }}' +# REQUEST_TYPE: '${{ steps.get_context.outputs.request_type }}' +# run: |- +# set -euo pipefail +# MESSAGE="@${GITHUB_ACTOR} I've received your request and I'm working on it now! 🤖" +# if [[ -n "${MESSAGE}" ]]; then +# gh issue comment "${ISSUE_NUMBER}" \ +# --body "${MESSAGE}" \ +# --repo "${REPOSITORY}" +# fi +# +# - name: 'Get description' +# id: 'get_description' +# env: +# GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' +# IS_PR: '${{ steps.get_context.outputs.is_pr }}' +# ISSUE_NUMBER: '${{ steps.get_context.outputs.issue_number }}' +# run: |- +# set -euo pipefail +# if [[ "${IS_PR}" == "true" ]]; then +# DESCRIPTION=$(gh pr view "${ISSUE_NUMBER}" --json body --template '{{.body}}') +# else +# DESCRIPTION=$(gh issue view "${ISSUE_NUMBER}" --json body --template '{{.body}}') +# fi +# { +# echo "description<> "${GITHUB_OUTPUT}" +# +# - name: 'Get comments' +# id: 'get_comments' +# env: +# GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' +# IS_PR: '${{ steps.get_context.outputs.is_pr }}' +# ISSUE_NUMBER: '${{ steps.get_context.outputs.issue_number }}' +# run: |- +# set -euo pipefail +# if [[ "${IS_PR}" == "true" ]]; then +# COMMENTS=$(gh pr view "${ISSUE_NUMBER}" --json comments --template '{{range .comments}}{{.author.login}}: {{.body}}{{"\n"}}{{end}}') +# else +# COMMENTS=$(gh issue view "${ISSUE_NUMBER}" --json comments --template '{{range .comments}}{{.author.login}}: {{.body}}{{"\n"}}{{end}}') +# fi +# { +# echo "comments<> "${GITHUB_OUTPUT}" +# +# - name: 'Run Gemini' +# id: 'run_gemini' +# uses: 'google-github-actions/run-gemini-cli@v0' +# env: +# GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' +# REPOSITORY: '${{ github.repository }}' +# USER_REQUEST: '${{ steps.get_context.outputs.user_request }}' +# ISSUE_NUMBER: '${{ steps.get_context.outputs.issue_number }}' +# IS_PR: '${{ steps.get_context.outputs.is_pr }}' +# with: +# gemini_api_key: '${{ secrets.GEMINI_API_KEY }}' +# gcp_workload_identity_provider: '${{ vars.GCP_WIF_PROVIDER }}' +# gcp_project_id: '${{ vars.GOOGLE_CLOUD_PROJECT }}' +# gcp_location: '${{ vars.GOOGLE_CLOUD_LOCATION }}' +# gcp_service_account: '${{ vars.SERVICE_ACCOUNT_EMAIL }}' +# use_vertex_ai: '${{ vars.GOOGLE_GENAI_USE_VERTEXAI }}' +# use_gemini_code_assist: '${{ vars.GOOGLE_GENAI_USE_GCA }}' +# settings: |- +# { +# "maxSessionTurns": 50, +# "telemetry": { +# "enabled": false, +# "target": "gcp" +# } +# } +# prompt: |- +# ## Role +# +# You are a helpful AI assistant invoked via a CLI interface in a GitHub workflow. You have access to tools to interact with the repository and respond to the user. +# +# ## Context +# +# - **Repository**: `${{ github.repository }}` +# - **Triggering Event**: `${{ github.event_name }}` +# - **Issue/PR Number**: `${{ steps.get_context.outputs.issue_number }}` +# - **Is this a PR?**: `${{ steps.get_context.outputs.is_pr }}` +# - **Issue/PR Description**: +# `${{ steps.get_description.outputs.description }}` +# - **Comments**: +# `${{ steps.get_comments.outputs.comments }}` +# +# ## User Request +# +# The user has sent the following request: +# `${{ steps.get_context.outputs.user_request }}` +# +# ## How to Respond to Issues, PR Comments, and Questions +# +# This workflow supports three main scenarios: +# +# 1. **Creating a Fix for an Issue** +# - Carefully read the user request and the related issue or PR description. +# - Use available tools to gather all relevant context (e.g., `gh issue view`, `gh pr view`, `gh pr diff`, `cat`, `head`, `tail`). +# - Identify the root cause of the problem before proceeding. +# - **Show and maintain a plan as a checklist**: +# - At the very beginning, outline the steps needed to resolve the issue or address the request and post them as a checklist comment on the issue or PR (use GitHub markdown checkboxes: `- [ ] Task`). +# - Example: +# ``` +# ### Plan +# - [ ] Investigate the root cause +# - [ ] Implement the fix in `file.py` +# - [ ] Add/modify tests +# - [ ] Update documentation +# - [ ] Verify the fix and close the issue +# ``` +# - Use: `gh pr comment "${ISSUE_NUMBER}" --body ""` or `gh issue comment "${ISSUE_NUMBER}" --body ""` to post the initial plan. +# - As you make progress, keep the checklist visible and up to date by editing the same comment (check off completed tasks with `- [x]`). +# - To update the checklist: +# 1. Find the comment ID for the checklist (use `gh pr comment list "${ISSUE_NUMBER}"` or `gh issue comment list "${ISSUE_NUMBER}"`). +# 2. Edit the comment with the updated checklist: +# - For PRs: `gh pr comment --edit --body ""` +# - For Issues: `gh issue comment --edit --body ""` +# 3. The checklist should only be maintained as a comment on the issue or PR. Do not track or update the checklist in code files. +# - If the fix requires code changes, determine which files and lines are affected. If clarification is needed, note any questions for the user. +# - Make the necessary code or documentation changes using the available tools (e.g., `write_file`). Ensure all changes follow project conventions and best practices. Reference all shell variables as `"${VAR}"` (with quotes and braces) to prevent errors. +# - Run any relevant tests or checks to verify the fix works as intended. If possible, provide evidence (test output, screenshots, etc.) that the issue is resolved. +# - **Branching and Committing**: +# - **NEVER commit directly to the `main` branch.** +# - If you are working on a **pull request** (`IS_PR` is `true`), the correct branch is already checked out. Simply commit and push to it. +# - `git add .` +# - `git commit -m "feat: "` +# - `git push` +# - If you are working on an **issue** (`IS_PR` is `false`), create a new branch for your changes. A good branch name would be `issue/${ISSUE_NUMBER}/`. +# - `git checkout -b issue/${ISSUE_NUMBER}/my-fix` +# - `git add .` +# - `git commit -m "feat: "` +# - `git push origin issue/${ISSUE_NUMBER}/my-fix` +# - After pushing, you can create a pull request: `gh pr create --title "Fixes #${ISSUE_NUMBER}: " --body "This PR addresses issue #${ISSUE_NUMBER}."` +# - Summarize what was changed and why in a markdown file: `write_file("response.md", "")` +# - Post the response as a comment: +# - For PRs: `gh pr comment "${ISSUE_NUMBER}" --body-file response.md` +# - For Issues: `gh issue comment "${ISSUE_NUMBER}" --body-file response.md` +# +# 2. **Addressing Comments on a Pull Request** +# - Read the specific comment and the context of the PR. +# - Use tools like `gh pr view`, `gh pr diff`, and `cat` to understand the code and discussion. +# - If the comment requests a change or clarification, follow the same process as for fixing an issue: create a checklist plan, implement, test, and commit any required changes, updating the checklist as you go. +# - **Committing Changes**: The correct PR branch is already checked out. Simply add, commit, and push your changes. +# - `git add .` +# - `git commit -m "fix: address review comments"` +# - `git push` +# - If the comment is a question, answer it directly and clearly, referencing code or documentation as needed. +# - Document your response in `response.md` and post it as a PR comment: `gh pr comment "${ISSUE_NUMBER}" --body-file response.md` +# +# 3. **Answering Any Question on an Issue** +# - Read the question and the full issue context using `gh issue view` and related tools. +# - Research or analyze the codebase as needed to provide an accurate answer. +# - If the question requires code or documentation changes, follow the fix process above, including creating and updating a checklist plan and **creating a new branch for your changes as described in section 1.** +# - Write a clear, concise answer in `response.md` and post it as an issue comment: `gh issue comment "${ISSUE_NUMBER}" --body-file response.md` +# +# ## Guidelines +# +# - **Be concise and actionable.** Focus on solving the user's problem efficiently. +# - **Always commit and push your changes if you modify code or documentation.** +# - **If you are unsure about the fix or answer, explain your reasoning and ask clarifying questions.** +# - **Follow project conventions and best practices.** diff --git a/.github/workflows/gemini-issue-automated-triage.yml b/.github/workflows/gemini-issue-automated-triage.yml index b0b0beafc7..d4ae486fd6 100644 --- a/.github/workflows/gemini-issue-automated-triage.yml +++ b/.github/workflows/gemini-issue-automated-triage.yml @@ -1,123 +1,123 @@ -name: '🏷️ Gemini Automated Issue Triage' - -on: - issues: - types: - - 'opened' - - 'reopened' - issue_comment: - types: - - 'created' - workflow_dispatch: - inputs: - issue_number: - description: 'issue number to triage' - required: true - type: 'number' - -concurrency: - group: '${{ github.workflow }}-${{ github.event.issue.number }}' - cancel-in-progress: true - -defaults: - run: - shell: 'bash' - -permissions: - contents: 'read' - id-token: 'write' - issues: 'write' - statuses: 'write' - -jobs: - triage-issue: - if: |- - github.event_name == 'issues' || - github.event_name == 'workflow_dispatch' || - ( - github.event_name == 'issue_comment' && - contains(github.event.comment.body, '@gemini-cli /triage') && - contains(fromJSON('["OWNER", "MEMBER", "COLLABORATOR"]'), github.event.comment.author_association) - ) - timeout-minutes: 5 - runs-on: 'ubuntu-latest' - - steps: - - name: 'Checkout repository' - uses: 'actions/checkout@v5' - - - name: 'Run Gemini Issue Triage' - uses: 'google-github-actions/run-gemini-cli@v0' - id: 'gemini_issue_triage' - env: - GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' - ISSUE_TITLE: '${{ github.event.issue.title }}' - ISSUE_BODY: '${{ github.event.issue.body }}' - ISSUE_NUMBER: '${{ github.event.issue.number }}' - REPOSITORY: '${{ github.repository }}' - with: - gemini_cli_version: '${{ vars.GEMINI_CLI_VERSION }}' - gcp_workload_identity_provider: '${{ vars.GCP_WIF_PROVIDER }}' - gcp_project_id: '${{ vars.GOOGLE_CLOUD_PROJECT }}' - gcp_location: '${{ vars.GOOGLE_CLOUD_LOCATION }}' - gcp_service_account: '${{ vars.SERVICE_ACCOUNT_EMAIL }}' - gemini_api_key: '${{ secrets.GEMINI_API_KEY }}' - use_vertex_ai: '${{ vars.GOOGLE_GENAI_USE_VERTEXAI }}' - use_gemini_code_assist: '${{ vars.GOOGLE_GENAI_USE_GCA }}' - settings: |- - { - "maxSessionTurns": 25, - "coreTools": [ - "run_shell_command(echo)", - "run_shell_command(gh label list)", - "run_shell_command(gh issue edit)" - ], - "telemetry": { - "enabled": true, - "target": "gcp" - } - } - prompt: |- - ## Role - - You are an issue triage assistant. Analyze the current GitHub issue - and apply the most appropriate existing labels. Use the available - tools to gather information; do not ask for information to be - provided. - - ## Steps - - 1. Run: `gh label list` to get all available labels. - 2. Review the issue title and body provided in the environment - variables: "${ISSUE_TITLE}" and "${ISSUE_BODY}". - 3. Classify issues by their type (bug, enhancement, documentation, - cleanup, etc) and their priority (p0, p1, p2, p3). Set the - labels according to the format `type: *` and `priority: *` patterns. - If the priority is determined to be more urgent than p2 (e.g. p0 or p1), mark the issue - as p2 and add a comment in the issue with the reason. The comment should ping - @blakeli0, @lqiu96, and @zhumin8 to notify them. - 4. Apply the selected labels to this issue using: - `gh issue edit "${ISSUE_NUMBER}" --add-label "label1,label2"` - - ## Guidelines - - - If there are already labels for `type: *` and `priority: *` set on the issue, do not modify the labels - - Only use labels that already exist in the repository - - Do not modify the original issue content - - Triage only the current issue - - Assign all applicable labels based on the issue content - - Reference all shell variables as "${VAR}" (with quotes and braces) - - - name: 'Post Issue Triage Failure Comment' - if: |- - ${{ failure() && steps.gemini_issue_triage.outcome == 'failure' }} - uses: 'actions/github-script@v7' - with: - github-token: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' - script: |- - github.rest.issues.createComment({ - owner: '${{ github.repository }}'.split('/')[0], - repo: '${{ github.repository }}'.split('/')[1], - issue_number: '${{ github.event.issue.number }}', - body: 'There is a problem with the Gemini CLI issue triaging. Please check the [action logs](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}) for details.' - }) +#name: '🏷️ Gemini Automated Issue Triage' +# +#on: +# issues: +# types: +# - 'opened' +# - 'reopened' +# issue_comment: +# types: +# - 'created' +# workflow_dispatch: +# inputs: +# issue_number: +# description: 'issue number to triage' +# required: true +# type: 'number' +# +#concurrency: +# group: '${{ github.workflow }}-${{ github.event.issue.number }}' +# cancel-in-progress: true +# +#defaults: +# run: +# shell: 'bash' +# +#permissions: +# contents: 'read' +# id-token: 'write' +# issues: 'write' +# statuses: 'write' +# +#jobs: +# triage-issue: +# if: |- +# github.event_name == 'issues' || +# github.event_name == 'workflow_dispatch' || +# ( +# github.event_name == 'issue_comment' && +# contains(github.event.comment.body, '@gemini-cli /triage') && +# contains(fromJSON('["OWNER", "MEMBER", "COLLABORATOR"]'), github.event.comment.author_association) +# ) +# timeout-minutes: 5 +# runs-on: 'ubuntu-latest' +# +# steps: +# - name: 'Checkout repository' +# uses: 'actions/checkout@v5' +# +# - name: 'Run Gemini Issue Triage' +# uses: 'google-github-actions/run-gemini-cli@v0' +# id: 'gemini_issue_triage' +# env: +# GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' +# ISSUE_TITLE: '${{ github.event.issue.title }}' +# ISSUE_BODY: '${{ github.event.issue.body }}' +# ISSUE_NUMBER: '${{ github.event.issue.number }}' +# REPOSITORY: '${{ github.repository }}' +# with: +# gemini_cli_version: '${{ vars.GEMINI_CLI_VERSION }}' +# gcp_workload_identity_provider: '${{ vars.GCP_WIF_PROVIDER }}' +# gcp_project_id: '${{ vars.GOOGLE_CLOUD_PROJECT }}' +# gcp_location: '${{ vars.GOOGLE_CLOUD_LOCATION }}' +# gcp_service_account: '${{ vars.SERVICE_ACCOUNT_EMAIL }}' +# gemini_api_key: '${{ secrets.GEMINI_API_KEY }}' +# use_vertex_ai: '${{ vars.GOOGLE_GENAI_USE_VERTEXAI }}' +# use_gemini_code_assist: '${{ vars.GOOGLE_GENAI_USE_GCA }}' +# settings: |- +# { +# "maxSessionTurns": 25, +# "coreTools": [ +# "run_shell_command(echo)", +# "run_shell_command(gh label list)", +# "run_shell_command(gh issue edit)" +# ], +# "telemetry": { +# "enabled": true, +# "target": "gcp" +# } +# } +# prompt: |- +# ## Role +# +# You are an issue triage assistant. Analyze the current GitHub issue +# and apply the most appropriate existing labels. Use the available +# tools to gather information; do not ask for information to be +# provided. +# +# ## Steps +# +# 1. Run: `gh label list` to get all available labels. +# 2. Review the issue title and body provided in the environment +# variables: "${ISSUE_TITLE}" and "${ISSUE_BODY}". +# 3. Classify issues by their type (bug, enhancement, documentation, +# cleanup, etc) and their priority (p0, p1, p2, p3). Set the +# labels according to the format `type: *` and `priority: *` patterns. +# If the priority is determined to be more urgent than p2 (e.g. p0 or p1), mark the issue +# as p2 and add a comment in the issue with the reason. The comment should ping +# @blakeli0, @lqiu96, and @zhumin8 to notify them. +# 4. Apply the selected labels to this issue using: +# `gh issue edit "${ISSUE_NUMBER}" --add-label "label1,label2"` +# +# ## Guidelines +# +# - If there are already labels for `type: *` and `priority: *` set on the issue, do not modify the labels +# - Only use labels that already exist in the repository +# - Do not modify the original issue content +# - Triage only the current issue +# - Assign all applicable labels based on the issue content +# - Reference all shell variables as "${VAR}" (with quotes and braces) +# +# - name: 'Post Issue Triage Failure Comment' +# if: |- +# ${{ failure() && steps.gemini_issue_triage.outcome == 'failure' }} +# uses: 'actions/github-script@v7' +# with: +# github-token: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' +# script: |- +# github.rest.issues.createComment({ +# owner: '${{ github.repository }}'.split('/')[0], +# repo: '${{ github.repository }}'.split('/')[1], +# issue_number: '${{ github.event.issue.number }}', +# body: 'There is a problem with the Gemini CLI issue triaging. Please check the [action logs](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}) for details.' +# }) diff --git a/.github/workflows/gemini-issue-scheduled-triage.yml b/.github/workflows/gemini-issue-scheduled-triage.yml index c16294eb13..3bb666b759 100644 --- a/.github/workflows/gemini-issue-scheduled-triage.yml +++ b/.github/workflows/gemini-issue-scheduled-triage.yml @@ -1,112 +1,112 @@ -name: '📋 Gemini Scheduled Issue Triage' - -on: - schedule: - - cron: '0 0 * * *' # Runs every day - workflow_dispatch: - -concurrency: - group: '${{ github.workflow }}' - cancel-in-progress: true - -defaults: - run: - shell: 'bash' - -permissions: - contents: 'read' - id-token: 'write' - issues: 'write' - statuses: 'write' - -jobs: - triage-issues: - timeout-minutes: 5 - runs-on: 'ubuntu-latest' - - steps: - - name: 'Checkout repository' - uses: 'actions/checkout@v5' - - - name: 'Find untriaged issues' - id: 'find_issues' - env: - GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' - GITHUB_REPOSITORY: '${{ github.repository }}' - GITHUB_OUTPUT: '${{ github.output }}' - run: |- - set -euo pipefail - - echo '🔍 Finding issues without labels...' - NO_LABEL_ISSUES="$(gh issue list --repo "${GITHUB_REPOSITORY}" \ - --search 'is:open is:issue no:label' --json number,title,body)" - - echo '🔄 Merging and deduplicating issues...' - ISSUES="$(echo "${NO_LABEL_ISSUES}" "${NEED_TRIAGE_ISSUES}" | jq -c -s 'add | unique_by(.number)')" - - echo '📝 Setting output for GitHub Actions...' - echo "issues_to_triage=${ISSUES}" >> "${GITHUB_OUTPUT}" - - ISSUE_COUNT="$(echo "${ISSUES}" | jq 'length')" - echo "✅ Found ${ISSUE_COUNT} issues to triage! 🎯" - - - name: 'Run Gemini Issue Triage' - if: |- - ${{ steps.find_issues.outputs.issues_to_triage != '[]' }} - uses: 'google-github-actions/run-gemini-cli@v0' - id: 'gemini_issue_triage' - env: - GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' - ISSUES_TO_TRIAGE: '${{ steps.find_issues.outputs.issues_to_triage }}' - REPOSITORY: '${{ github.repository }}' - with: - gemini_cli_version: '${{ vars.GEMINI_CLI_VERSION }}' - gcp_workload_identity_provider: '${{ vars.GCP_WIF_PROVIDER }}' - gcp_project_id: '${{ vars.GOOGLE_CLOUD_PROJECT }}' - gcp_location: '${{ vars.GOOGLE_CLOUD_LOCATION }}' - gcp_service_account: '${{ vars.SERVICE_ACCOUNT_EMAIL }}' - gemini_api_key: '${{ secrets.GEMINI_API_KEY }}' - use_vertex_ai: '${{ vars.GOOGLE_GENAI_USE_VERTEXAI }}' - use_gemini_code_assist: '${{ vars.GOOGLE_GENAI_USE_GCA }}' - settings: |- - { - "maxSessionTurns": 25, - "coreTools": [ - "run_shell_command(echo)", - "run_shell_command(gh label list)", - "run_shell_command(gh issue edit)", - "run_shell_command(gh issue list)" - ], - "telemetry": { - "enabled": true, - "target": "gcp" - } - } - prompt: |- - ## Role - - You are an issue triage assistant. Analyze issues and apply - appropriate labels. Use the available tools to gather information; - do not ask for information to be provided. - - ## Steps - - 1. Run: `gh label list` - 2. Check environment variable: "${ISSUES_TO_TRIAGE}" (JSON array - of issues) - 3. Classify each issue by their type (bug, enhancement, documentation, - cleanup, etc) and their priority (p0, p1, p2, p3). Set the - labels according to the format `type: *` and `priority: *` patterns. - If the priority is determined to be more urgent than p2 (e.g. p0 or p1), mark the issue - as p2 and add a comment in the issue with the reason. The comment should ping - @blakeli0, @lqiu96, and @zhumin8 to notify them. - 4. Apply the selected labels to this issue using: - `gh issue edit "${ISSUE_NUMBER}" --add-label "label1,label2"` - - ## Guidelines - - - If there are already labels for `type: *` and `priority: *` set on the issue, do not modify the labels - - Only use existing repository labels - - Do not modify the original issue content - - Triage each issue independently - - Reference all shell variables as "${VAR}" (with quotes and braces) \ No newline at end of file +#name: '📋 Gemini Scheduled Issue Triage' +# +#on: +# schedule: +# - cron: '0 0 * * *' # Runs every day +# workflow_dispatch: +# +#concurrency: +# group: '${{ github.workflow }}' +# cancel-in-progress: true +# +#defaults: +# run: +# shell: 'bash' +# +#permissions: +# contents: 'read' +# id-token: 'write' +# issues: 'write' +# statuses: 'write' +# +#jobs: +# triage-issues: +# timeout-minutes: 5 +# runs-on: 'ubuntu-latest' +# +# steps: +# - name: 'Checkout repository' +# uses: 'actions/checkout@v5' +# +# - name: 'Find untriaged issues' +# id: 'find_issues' +# env: +# GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' +# GITHUB_REPOSITORY: '${{ github.repository }}' +# GITHUB_OUTPUT: '${{ github.output }}' +# run: |- +# set -euo pipefail +# +# echo '🔍 Finding issues without labels...' +# NO_LABEL_ISSUES="$(gh issue list --repo "${GITHUB_REPOSITORY}" \ +# --search 'is:open is:issue no:label' --json number,title,body)" +# +# echo '🔄 Merging and deduplicating issues...' +# ISSUES="$(echo "${NO_LABEL_ISSUES}" "${NEED_TRIAGE_ISSUES}" | jq -c -s 'add | unique_by(.number)')" +# +# echo '📝 Setting output for GitHub Actions...' +# echo "issues_to_triage=${ISSUES}" >> "${GITHUB_OUTPUT}" +# +# ISSUE_COUNT="$(echo "${ISSUES}" | jq 'length')" +# echo "✅ Found ${ISSUE_COUNT} issues to triage! 🎯" +# +# - name: 'Run Gemini Issue Triage' +# if: |- +# ${{ steps.find_issues.outputs.issues_to_triage != '[]' }} +# uses: 'google-github-actions/run-gemini-cli@v0' +# id: 'gemini_issue_triage' +# env: +# GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' +# ISSUES_TO_TRIAGE: '${{ steps.find_issues.outputs.issues_to_triage }}' +# REPOSITORY: '${{ github.repository }}' +# with: +# gemini_cli_version: '${{ vars.GEMINI_CLI_VERSION }}' +# gcp_workload_identity_provider: '${{ vars.GCP_WIF_PROVIDER }}' +# gcp_project_id: '${{ vars.GOOGLE_CLOUD_PROJECT }}' +# gcp_location: '${{ vars.GOOGLE_CLOUD_LOCATION }}' +# gcp_service_account: '${{ vars.SERVICE_ACCOUNT_EMAIL }}' +# gemini_api_key: '${{ secrets.GEMINI_API_KEY }}' +# use_vertex_ai: '${{ vars.GOOGLE_GENAI_USE_VERTEXAI }}' +# use_gemini_code_assist: '${{ vars.GOOGLE_GENAI_USE_GCA }}' +# settings: |- +# { +# "maxSessionTurns": 25, +# "coreTools": [ +# "run_shell_command(echo)", +# "run_shell_command(gh label list)", +# "run_shell_command(gh issue edit)", +# "run_shell_command(gh issue list)" +# ], +# "telemetry": { +# "enabled": true, +# "target": "gcp" +# } +# } +# prompt: |- +# ## Role +# +# You are an issue triage assistant. Analyze issues and apply +# appropriate labels. Use the available tools to gather information; +# do not ask for information to be provided. +# +# ## Steps +# +# 1. Run: `gh label list` +# 2. Check environment variable: "${ISSUES_TO_TRIAGE}" (JSON array +# of issues) +# 3. Classify each issue by their type (bug, enhancement, documentation, +# cleanup, etc) and their priority (p0, p1, p2, p3). Set the +# labels according to the format `type: *` and `priority: *` patterns. +# If the priority is determined to be more urgent than p2 (e.g. p0 or p1), mark the issue +# as p2 and add a comment in the issue with the reason. The comment should ping +# @blakeli0, @lqiu96, and @zhumin8 to notify them. +# 4. Apply the selected labels to this issue using: +# `gh issue edit "${ISSUE_NUMBER}" --add-label "label1,label2"` +# +# ## Guidelines +# +# - If there are already labels for `type: *` and `priority: *` set on the issue, do not modify the labels +# - Only use existing repository labels +# - Do not modify the original issue content +# - Triage each issue independently +# - Reference all shell variables as "${VAR}" (with quotes and braces) \ No newline at end of file diff --git a/.github/workflows/gemini-pr-review.yml b/.github/workflows/gemini-pr-review.yml index fe4d3c4455..76d7921d39 100644 --- a/.github/workflows/gemini-pr-review.yml +++ b/.github/workflows/gemini-pr-review.yml @@ -1,428 +1,428 @@ -name: '🧐 Gemini Pull Request Review' - -on: - pull_request: - types: [opened, reopened] - issue_comment: - types: [created] - workflow_dispatch: - inputs: - pr_number: - description: 'PR number to review' - required: true - type: 'number' - -concurrency: - group: '${{ github.workflow }}-${{ github.head_ref || github.ref }}' - cancel-in-progress: true - -defaults: - run: - shell: 'bash' - -permissions: - contents: 'read' - id-token: 'write' - issues: 'write' - pull-requests: 'write' - statuses: 'write' - -jobs: - review-pr: - if: |- - github.event_name == 'workflow_dispatch' || - ( - github.event_name == 'pull_request' && - contains(fromJSON('["OWNER", "MEMBER", "COLLABORATOR"]'), github.event.pull_request.author_association) - ) || - ( - github.event_name == 'issue_comment' && - github.event.issue.pull_request && - contains(github.event.comment.body, '@gemini-cli /review') && - contains(fromJSON('["OWNER", "MEMBER", "COLLABORATOR"]'), github.event.comment.author_association) - ) - timeout-minutes: 5 - runs-on: 'ubuntu-latest' - - steps: - - name: 'Checkout PR code' - uses: 'actions/checkout@v5' - - - name: 'Get PR details (pull_request & workflow_dispatch)' - id: 'get_pr' - if: |- - ${{ github.event_name == 'pull_request' || github.event_name == 'workflow_dispatch' }} - env: - GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' - EVENT_NAME: '${{ github.event_name }}' - WORKFLOW_PR_NUMBER: '${{ github.event.inputs.pr_number }}' - PULL_REQUEST_NUMBER: '${{ github.event.pull_request.number }}' - run: |- - set -euo pipefail - - if [[ "${EVENT_NAME}" = "workflow_dispatch" ]]; then - PR_NUMBER="${WORKFLOW_PR_NUMBER}" - else - PR_NUMBER="${PULL_REQUEST_NUMBER}" - fi - - echo "pr_number=${PR_NUMBER}" >> "${GITHUB_OUTPUT}" - - # Get PR details - PR_DATA="$(gh pr view "${PR_NUMBER}" --json title,body,additions,deletions,changedFiles,baseRefName,headRefName)" - echo "pr_data=${PR_DATA}" >> "${GITHUB_OUTPUT}" - - # Get file changes - CHANGED_FILES="$(gh pr diff "${PR_NUMBER}" --name-only)" - { - echo "changed_files<> "${GITHUB_OUTPUT}" - - - - name: 'Get PR details (issue_comment)' - id: 'get_pr_comment' - if: |- - ${{ github.event_name == 'issue_comment' }} - env: - GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' - COMMENT_BODY: '${{ github.event.comment.body }}' - PR_NUMBER: '${{ github.event.issue.number }}' - run: |- - set -euo pipefail - - echo "pr_number=${PR_NUMBER}" >> "${GITHUB_OUTPUT}" - - # Extract additional instructions from comment - ADDITIONAL_INSTRUCTIONS="$( - echo "${COMMENT_BODY}" | sed 's/.*@gemini-cli \/review//' | xargs - )" - echo "additional_instructions=${ADDITIONAL_INSTRUCTIONS}" >> "${GITHUB_OUTPUT}" - - # Get PR details - PR_DATA="$(gh pr view "${PR_NUMBER}" --json title,body,additions,deletions,changedFiles,baseRefName,headRefName)" - echo "pr_data=${PR_DATA}" >> "${GITHUB_OUTPUT}" - - # Get file changes - CHANGED_FILES="$(gh pr diff "${PR_NUMBER}" --name-only)" - { - echo "changed_files<> "${GITHUB_OUTPUT}" - - - name: 'Run Gemini PR Review' - uses: 'google-github-actions/run-gemini-cli@v0' - id: 'gemini_pr_review' - env: - GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' - PR_NUMBER: '${{ steps.get_pr.outputs.pr_number || steps.get_pr_comment.outputs.pr_number }}' - PR_DATA: '${{ steps.get_pr.outputs.pr_data || steps.get_pr_comment.outputs.pr_data }}' - CHANGED_FILES: '${{ steps.get_pr.outputs.changed_files || steps.get_pr_comment.outputs.changed_files }}' - ADDITIONAL_INSTRUCTIONS: '${{ steps.get_pr.outputs.additional_instructions || steps.get_pr_comment.outputs.additional_instructions }}' - REPOSITORY: '${{ github.repository }}' - with: - gemini_cli_version: '${{ vars.GEMINI_CLI_VERSION }}' - gcp_workload_identity_provider: '${{ vars.GCP_WIF_PROVIDER }}' - gcp_project_id: '${{ vars.GOOGLE_CLOUD_PROJECT }}' - gcp_location: '${{ vars.GOOGLE_CLOUD_LOCATION }}' - gcp_service_account: '${{ vars.SERVICE_ACCOUNT_EMAIL }}' - gemini_api_key: '${{ secrets.GEMINI_API_KEY }}' - use_vertex_ai: '${{ vars.GOOGLE_GENAI_USE_VERTEXAI }}' - use_gemini_code_assist: '${{ vars.GOOGLE_GENAI_USE_GCA }}' - settings: |- - { - "maxSessionTurns": 20, - "mcpServers": { - "github": { - "command": "docker", - "args": [ - "run", - "-i", - "--rm", - "-e", - "GITHUB_PERSONAL_ACCESS_TOKEN", - "ghcr.io/github/github-mcp-server" - ], - "includeTools": [ - "create_pending_pull_request_review", - "add_comment_to_pending_review", - "submit_pending_pull_request_review" - ], - "env": { - "GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_TOKEN}" - } - } - }, - "coreTools": [ - "run_shell_command(echo)", - "run_shell_command(gh pr view)", - "run_shell_command(gh pr diff)", - "run_shell_command(cat)", - "run_shell_command(head)", - "run_shell_command(tail)", - "run_shell_command(grep)" - ], - "telemetry": { - "enabled": false, - "target": "gcp" - } - } - prompt: |- - ## Role - - You are an expert code reviewer. You have access to tools to gather - PR information and perform the review on GitHub. Use the available tools to - gather information; do not ask for information to be provided. - - ## Requirements - 1. All feedback must be left on GitHub. - 2. Any output that is not left in GitHub will not be seen. - - ## Steps - - Start by running these commands to gather the required data: - 1. Run: echo "${REPOSITORY}" to get the github repository in / format - 2. Run: echo "${PR_DATA}" to get PR details (JSON format) - 3. Run: echo "${CHANGED_FILES}" to get the list of changed files - 4. Run: echo "${PR_NUMBER}" to get the PR number - 5. Run: echo "${ADDITIONAL_INSTRUCTIONS}" to see any specific review - instructions from the user - 6. Run: gh pr diff "${PR_NUMBER}" to see the full diff and reference - Context section to understand it - 7. For any specific files, use: cat filename, head -50 filename, or - tail -50 filename - 8. If ADDITIONAL_INSTRUCTIONS contains text, prioritize those - specific areas or focus points in your review. Common instruction - examples: "focus on security", "check performance", "review error - handling", "check for breaking changes" - - ## Guideline - ### Core Guideline(Always applicable) - - 1. Understand the Context: Analyze the pull request title, description, changes, and code files to grasp the intent. - 2. Meticulous Review: Thoroughly review all relevant code changes, prioritizing added lines. Consider the specified - focus areas and any provided style guide. - 3. Comprehensive Review: Ensure that the code is thoroughly reviewed, as it's important to the author - that you identify any and all relevant issues (subject to the review criteria and style guide). - Missing any issues will lead to a poor code review experience for the author. - 4. Constructive Feedback: - * Provide clear explanations for each concern. - * Offer specific, improved code suggestions and suggest alternative approaches, when applicable. - Code suggestions in particular are very helpful so that the author can directly apply them - to their code, but they must be accurately anchored to the lines that should be replaced. - 5. Severity Indication: Clearly indicate the severity of the issue in the review comment. - This is very important to help the author understand the urgency of the issue. - The severity should be one of the following (which are provided below in decreasing order of severity): - * `critical`: This issue must be addressed immediately, as it could lead to serious consequences - for the code's correctness, security, or performance. - * `high`: This issue should be addressed soon, as it could cause problems in the future. - * `medium`: This issue should be considered for future improvement, but it's not critical or urgent. - * `low`: This issue is minor or stylistic, and can be addressed at the author's discretion. - 6. Avoid commenting on hardcoded dates and times being in future or not (for example "this date is in the future"). - * Remember you don't have access to the current date and time and leave that to the author. - 7. Targeted Suggestions: Limit all suggestions to only portions that are modified in the diff hunks. - This is a strict requirement as the GitHub (and other SCM's) API won't allow comments on parts of code files that are not - included in the diff hunks. - 8. Code Suggestions in Review Comments: - * Succinctness: Aim to make code suggestions succinct, unless necessary. Larger code suggestions tend to be - harder for pull request authors to commit directly in the pull request UI. - * Valid Formatting: Provide code suggestions within the suggestion field of the JSON response (as a string literal, - escaping special characters like \n, \\, \"). Do not include markdown code blocks in the suggestion field. - Use markdown code blocks in the body of the comment only for broader examples or if a suggestion field would - create an excessively large diff. Prefer the suggestion field for specific, targeted code changes. - * Line Number Accuracy: Code suggestions need to align perfectly with the code it intend to replace. - Pay special attention to line numbers when creating comments, particularly if there is a code suggestion. - Note the patch includes code versions with line numbers for the before and after code snippets for each diff, so use these to anchor - your comments and corresponding code suggestions. - * Compilable: Code suggestions should be compilable code snippets that can be directly copy/pasted into the code file. - If the suggestion is not compilable, it will not be accepted by the pull request. Note that not all languages Are - compiled of course, so by compilable here, we mean either literally or in spirit. - * Inline Code Comments: Feel free to add brief comments to the code suggestion if it enhances the underlying code readability. - Just make sure that the inline code comments add value, and are not just restating what the code does. Don't use - inline comments to "teach" the author (use the review comment body directly for that), instead use it if it's beneficial - to the readability of the code itself. - 10. Markdown Formatting: Heavily leverage the benefits of markdown for formatting, such as bulleted lists, bold text, tables, etc. - 11. Avoid mistaken review comments: - * Any comment you make must point towards a discrepancy found in the code and the best practice surfaced in your feedback. - For example, if you are pointing out that constants need to be named in all caps with underscores, - ensure that the code selected by the comment does not already do this, otherwise it's confusing let alone unnecessary. - 12. Remove Duplicated code suggestions: - * Some provided code suggestions are duplicated, please remove the duplicated review comments. - 13. Don't Approve The Pull Request - 14. Reference all shell variables as "${VAR}" (with quotes and braces) - - ### Review Criteria (Prioritized in Review) - - * Correctness: Verify code functionality, handle edge cases, and ensure alignment between function - descriptions and implementations. Consider common correctness issues (logic errors, error handling, - race conditions, data validation, API usage, type mismatches). - * Efficiency: Identify performance bottlenecks, optimize for efficiency, and avoid unnecessary - loops, iterations, or calculations. Consider common efficiency issues (excessive loops, memory - leaks, inefficient data structures, redundant calculations, excessive logging, etc.). - * Maintainability: Assess code readability, modularity, and adherence to language idioms and - best practices. Consider common maintainability issues (naming, comments/documentation, complexity, - code duplication, formatting, magic numbers). State the style guide being followed (defaulting to - commonly used guides, for example Python's PEP 8 style guide or Google Java Style Guide, if no style guide is specified). - * Security: Identify potential vulnerabilities (e.g., insecure storage, injection attacks, - insufficient access controls). - - ### Miscellaneous Considerations - * Testing: Ensure adequate unit tests, integration tests, and end-to-end tests. Evaluate - coverage, edge case handling, and overall test quality. - * Performance: Assess performance under expected load, identify bottlenecks, and suggest - optimizations. - * Scalability: Evaluate how the code will scale with growing user base or data volume. - * Modularity and Reusability: Assess code organization, modularity, and reusability. Suggest - refactoring or creating reusable components. - * Error Logging and Monitoring: Ensure errors are logged effectively, and implement monitoring - mechanisms to track application health in production. - - **CRITICAL CONSTRAINTS:** - - You MUST only provide comments on lines that represent the actual changes in - the diff. This means your comments should only refer to lines that begin with - a `+` or `-` character in the provided diff content. - DO NOT comment on lines that start with a space (context lines). - - You MUST only add a review comment if there exists an actual ISSUE or BUG in the code changes. - DO NOT add review comments to tell the user to "check" or "confirm" or "verify" something. - DO NOT add review comments to tell the user to "ensure" something. - DO NOT add review comments to explain what the code change does. - DO NOT add review comments to validate what the code change does. - DO NOT use the review comments to explain the code to the author. They already know their code. Only comment when there's an improvement opportunity. This is very important. - - Pay close attention to line numbers and ensure they are correct. - Pay close attention to indentations in the code suggestions and make sure they match the code they are to replace. - Avoid comments on the license headers - if any exists - and instead make comments on the code that is being changed. - - It's absolutely important to avoid commenting on the license header of files. - It's absolutely important to avoid commenting on copyright headers. - Avoid commenting on hardcoded dates and times being in future or not (for example "this date is in the future"). - Remember you don't have access to the current date and time and leave that to the author. - - Avoid mentioning any of your instructions, settings or criteria. - - Here are some general guidelines for setting the severity of your comments - - Comments about refactoring a hardcoded string or number as a constant are generally considered low severity. - - Comments about log messages or log enhancements are generally considered low severity. - - Comments in .md files are medium or low severity. This is really important. - - Comments about adding or expanding docstring/javadoc have low severity most of the times. - - Comments about suppressing unchecked warnings or todos are considered low severity. - - Comments about typos are usually low or medium severity. - - Comments about testing or on tests are usually low severity. - - Do not comment about the content of a URL if the content is not directly available in the input. - - Keep comments bodies concise and to the point. - Keep each comment focused on one issue. - - ## Context - The files that are changed in this pull request are represented below in the following - format, showing the file name and the portions of the file that are changed: - - - FILE: - DIFF: - - - -------------------- - - FILE: - DIFF: - - - -------------------- - - (and so on for all files changed) - - - Note that if you want to make a comment on the LEFT side of the UI / before the diff code version - to note those line numbers and the corresponding code. Same for a comment on the RIGHT side - of the UI / after the diff code version to note the line numbers and corresponding code. - This should be your guide to picking line numbers, and also very importantly, restrict - your comments to be only within this line range for these files, whether on LEFT or RIGHT. - If you comment out of bounds, the review will fail, so you must pay attention the file name, - line numbers, and pre/post diff versions when crafting your comment. - - Here are the patches that were implemented in the pull request, per the - formatting above: - - The get the files changed in this pull request, run: - "$(gh pr diff "${PR_NUMBER}" --patch)" to get the list of changed files PATCH - - ## Review - - Once you have the information and are ready to leave a review on GitHub, post the review to GitHub using the GitHub MCP tool by: - 1. Creating a pending review: Use the mcp__github__create_pending_pull_request_review to create a Pending Pull Request Review. - - 2. Adding review comments: - 2.1 Use the mcp__github__add_comment_to_pending_review to add comments to the Pending Pull Request Review. Inline comments are preferred whenever possible, so repeat this step, calling mcp__github__add_comment_to_pending_review, as needed. All comments about specific lines of code should use inline comments. It is preferred to use code suggestions when possible, which include a code block that is labeled "suggestion", which contains what the new code should be. All comments should also have a severity. The syntax is: - Normal Comment Syntax: - - {{SEVERITY}} {{COMMENT_TEXT}} - - - Inline Comment Syntax: (Preferred): - - {{SEVERITY}} {{COMMENT_TEXT}} - ```suggestion - {{CODE_SUGGESTION}} - ``` - - - Prepend a severity emoji to each comment: - - 🟢 for low severity - - 🟡 for medium severity - - 🟠 for high severity - - 🔴 for critical severity - - 🔵 if severity is unclear - - Including all of this, an example inline comment would be: - - 🟢 Use camelCase for function names - ```suggestion - myFooBarFunction - ``` - - - A critical severity example would be: - - 🔴 Remove storage key from GitHub - ```suggestion - ``` - - 3. Posting the review: Use the mcp__github__submit_pending_pull_request_review to submit the Pending Pull Request Review. - - 3.1 Crafting the summary comment: Include a summary of high level points that were not addressed with inline comments. Be concise. Do not repeat details mentioned inline. - - Structure your summary comment using this exact format with markdown: - ## 📋 Review Summary - - Provide a brief 2-3 sentence overview of the PR and overall - assessment. - - ## 🔍 General Feedback - - List general observations about code quality - - Mention overall patterns or architectural decisions - - Highlight positive aspects of the implementation - - Note any recurring themes across files - - ## Final Instructions - - Remember, you are running in a VM and no one reviewing your output. Your review must be posted to GitHub using the MCP tools to create a pending review, add comments to the pending review, and submit the pending review. - - - - name: 'Post PR review failure comment' - if: |- - ${{ failure() && steps.gemini_pr_review.outcome == 'failure' }} - uses: 'actions/github-script@v7' - with: - github-token: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' - script: |- - github.rest.issues.createComment({ - owner: '${{ github.repository }}'.split('/')[0], - repo: '${{ github.repository }}'.split('/')[1], - issue_number: '${{ steps.get_pr.outputs.pr_number || steps.get_pr_comment.outputs.pr_number }}', - body: 'There is a problem with the Gemini CLI PR review. Please check the [action logs](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}) for details.' - }) +#name: '🧐 Gemini Pull Request Review' +# +#on: +# pull_request: +# types: [opened, reopened] +# issue_comment: +# types: [created] +# workflow_dispatch: +# inputs: +# pr_number: +# description: 'PR number to review' +# required: true +# type: 'number' +# +#concurrency: +# group: '${{ github.workflow }}-${{ github.head_ref || github.ref }}' +# cancel-in-progress: true +# +#defaults: +# run: +# shell: 'bash' +# +#permissions: +# contents: 'read' +# id-token: 'write' +# issues: 'write' +# pull-requests: 'write' +# statuses: 'write' +# +#jobs: +# review-pr: +# if: |- +# github.event_name == 'workflow_dispatch' || +# ( +# github.event_name == 'pull_request' && +# contains(fromJSON('["OWNER", "MEMBER", "COLLABORATOR"]'), github.event.pull_request.author_association) +# ) || +# ( +# github.event_name == 'issue_comment' && +# github.event.issue.pull_request && +# contains(github.event.comment.body, '@gemini-cli /review') && +# contains(fromJSON('["OWNER", "MEMBER", "COLLABORATOR"]'), github.event.comment.author_association) +# ) +# timeout-minutes: 5 +# runs-on: 'ubuntu-latest' +# +# steps: +# - name: 'Checkout PR code' +# uses: 'actions/checkout@v5' +# +# - name: 'Get PR details (pull_request & workflow_dispatch)' +# id: 'get_pr' +# if: |- +# ${{ github.event_name == 'pull_request' || github.event_name == 'workflow_dispatch' }} +# env: +# GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' +# EVENT_NAME: '${{ github.event_name }}' +# WORKFLOW_PR_NUMBER: '${{ github.event.inputs.pr_number }}' +# PULL_REQUEST_NUMBER: '${{ github.event.pull_request.number }}' +# run: |- +# set -euo pipefail +# +# if [[ "${EVENT_NAME}" = "workflow_dispatch" ]]; then +# PR_NUMBER="${WORKFLOW_PR_NUMBER}" +# else +# PR_NUMBER="${PULL_REQUEST_NUMBER}" +# fi +# +# echo "pr_number=${PR_NUMBER}" >> "${GITHUB_OUTPUT}" +# +# # Get PR details +# PR_DATA="$(gh pr view "${PR_NUMBER}" --json title,body,additions,deletions,changedFiles,baseRefName,headRefName)" +# echo "pr_data=${PR_DATA}" >> "${GITHUB_OUTPUT}" +# +# # Get file changes +# CHANGED_FILES="$(gh pr diff "${PR_NUMBER}" --name-only)" +# { +# echo "changed_files<> "${GITHUB_OUTPUT}" +# +# +# - name: 'Get PR details (issue_comment)' +# id: 'get_pr_comment' +# if: |- +# ${{ github.event_name == 'issue_comment' }} +# env: +# GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' +# COMMENT_BODY: '${{ github.event.comment.body }}' +# PR_NUMBER: '${{ github.event.issue.number }}' +# run: |- +# set -euo pipefail +# +# echo "pr_number=${PR_NUMBER}" >> "${GITHUB_OUTPUT}" +# +# # Extract additional instructions from comment +# ADDITIONAL_INSTRUCTIONS="$( +# echo "${COMMENT_BODY}" | sed 's/.*@gemini-cli \/review//' | xargs +# )" +# echo "additional_instructions=${ADDITIONAL_INSTRUCTIONS}" >> "${GITHUB_OUTPUT}" +# +# # Get PR details +# PR_DATA="$(gh pr view "${PR_NUMBER}" --json title,body,additions,deletions,changedFiles,baseRefName,headRefName)" +# echo "pr_data=${PR_DATA}" >> "${GITHUB_OUTPUT}" +# +# # Get file changes +# CHANGED_FILES="$(gh pr diff "${PR_NUMBER}" --name-only)" +# { +# echo "changed_files<> "${GITHUB_OUTPUT}" +# +# - name: 'Run Gemini PR Review' +# uses: 'google-github-actions/run-gemini-cli@v0' +# id: 'gemini_pr_review' +# env: +# GITHUB_TOKEN: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' +# PR_NUMBER: '${{ steps.get_pr.outputs.pr_number || steps.get_pr_comment.outputs.pr_number }}' +# PR_DATA: '${{ steps.get_pr.outputs.pr_data || steps.get_pr_comment.outputs.pr_data }}' +# CHANGED_FILES: '${{ steps.get_pr.outputs.changed_files || steps.get_pr_comment.outputs.changed_files }}' +# ADDITIONAL_INSTRUCTIONS: '${{ steps.get_pr.outputs.additional_instructions || steps.get_pr_comment.outputs.additional_instructions }}' +# REPOSITORY: '${{ github.repository }}' +# with: +# gemini_cli_version: '${{ vars.GEMINI_CLI_VERSION }}' +# gcp_workload_identity_provider: '${{ vars.GCP_WIF_PROVIDER }}' +# gcp_project_id: '${{ vars.GOOGLE_CLOUD_PROJECT }}' +# gcp_location: '${{ vars.GOOGLE_CLOUD_LOCATION }}' +# gcp_service_account: '${{ vars.SERVICE_ACCOUNT_EMAIL }}' +# gemini_api_key: '${{ secrets.GEMINI_API_KEY }}' +# use_vertex_ai: '${{ vars.GOOGLE_GENAI_USE_VERTEXAI }}' +# use_gemini_code_assist: '${{ vars.GOOGLE_GENAI_USE_GCA }}' +# settings: |- +# { +# "maxSessionTurns": 20, +# "mcpServers": { +# "github": { +# "command": "docker", +# "args": [ +# "run", +# "-i", +# "--rm", +# "-e", +# "GITHUB_PERSONAL_ACCESS_TOKEN", +# "ghcr.io/github/github-mcp-server" +# ], +# "includeTools": [ +# "create_pending_pull_request_review", +# "add_comment_to_pending_review", +# "submit_pending_pull_request_review" +# ], +# "env": { +# "GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_TOKEN}" +# } +# } +# }, +# "coreTools": [ +# "run_shell_command(echo)", +# "run_shell_command(gh pr view)", +# "run_shell_command(gh pr diff)", +# "run_shell_command(cat)", +# "run_shell_command(head)", +# "run_shell_command(tail)", +# "run_shell_command(grep)" +# ], +# "telemetry": { +# "enabled": false, +# "target": "gcp" +# } +# } +# prompt: |- +# ## Role +# +# You are an expert code reviewer. You have access to tools to gather +# PR information and perform the review on GitHub. Use the available tools to +# gather information; do not ask for information to be provided. +# +# ## Requirements +# 1. All feedback must be left on GitHub. +# 2. Any output that is not left in GitHub will not be seen. +# +# ## Steps +# +# Start by running these commands to gather the required data: +# 1. Run: echo "${REPOSITORY}" to get the github repository in / format +# 2. Run: echo "${PR_DATA}" to get PR details (JSON format) +# 3. Run: echo "${CHANGED_FILES}" to get the list of changed files +# 4. Run: echo "${PR_NUMBER}" to get the PR number +# 5. Run: echo "${ADDITIONAL_INSTRUCTIONS}" to see any specific review +# instructions from the user +# 6. Run: gh pr diff "${PR_NUMBER}" to see the full diff and reference +# Context section to understand it +# 7. For any specific files, use: cat filename, head -50 filename, or +# tail -50 filename +# 8. If ADDITIONAL_INSTRUCTIONS contains text, prioritize those +# specific areas or focus points in your review. Common instruction +# examples: "focus on security", "check performance", "review error +# handling", "check for breaking changes" +# +# ## Guideline +# ### Core Guideline(Always applicable) +# +# 1. Understand the Context: Analyze the pull request title, description, changes, and code files to grasp the intent. +# 2. Meticulous Review: Thoroughly review all relevant code changes, prioritizing added lines. Consider the specified +# focus areas and any provided style guide. +# 3. Comprehensive Review: Ensure that the code is thoroughly reviewed, as it's important to the author +# that you identify any and all relevant issues (subject to the review criteria and style guide). +# Missing any issues will lead to a poor code review experience for the author. +# 4. Constructive Feedback: +# * Provide clear explanations for each concern. +# * Offer specific, improved code suggestions and suggest alternative approaches, when applicable. +# Code suggestions in particular are very helpful so that the author can directly apply them +# to their code, but they must be accurately anchored to the lines that should be replaced. +# 5. Severity Indication: Clearly indicate the severity of the issue in the review comment. +# This is very important to help the author understand the urgency of the issue. +# The severity should be one of the following (which are provided below in decreasing order of severity): +# * `critical`: This issue must be addressed immediately, as it could lead to serious consequences +# for the code's correctness, security, or performance. +# * `high`: This issue should be addressed soon, as it could cause problems in the future. +# * `medium`: This issue should be considered for future improvement, but it's not critical or urgent. +# * `low`: This issue is minor or stylistic, and can be addressed at the author's discretion. +# 6. Avoid commenting on hardcoded dates and times being in future or not (for example "this date is in the future"). +# * Remember you don't have access to the current date and time and leave that to the author. +# 7. Targeted Suggestions: Limit all suggestions to only portions that are modified in the diff hunks. +# This is a strict requirement as the GitHub (and other SCM's) API won't allow comments on parts of code files that are not +# included in the diff hunks. +# 8. Code Suggestions in Review Comments: +# * Succinctness: Aim to make code suggestions succinct, unless necessary. Larger code suggestions tend to be +# harder for pull request authors to commit directly in the pull request UI. +# * Valid Formatting: Provide code suggestions within the suggestion field of the JSON response (as a string literal, +# escaping special characters like \n, \\, \"). Do not include markdown code blocks in the suggestion field. +# Use markdown code blocks in the body of the comment only for broader examples or if a suggestion field would +# create an excessively large diff. Prefer the suggestion field for specific, targeted code changes. +# * Line Number Accuracy: Code suggestions need to align perfectly with the code it intend to replace. +# Pay special attention to line numbers when creating comments, particularly if there is a code suggestion. +# Note the patch includes code versions with line numbers for the before and after code snippets for each diff, so use these to anchor +# your comments and corresponding code suggestions. +# * Compilable: Code suggestions should be compilable code snippets that can be directly copy/pasted into the code file. +# If the suggestion is not compilable, it will not be accepted by the pull request. Note that not all languages Are +# compiled of course, so by compilable here, we mean either literally or in spirit. +# * Inline Code Comments: Feel free to add brief comments to the code suggestion if it enhances the underlying code readability. +# Just make sure that the inline code comments add value, and are not just restating what the code does. Don't use +# inline comments to "teach" the author (use the review comment body directly for that), instead use it if it's beneficial +# to the readability of the code itself. +# 10. Markdown Formatting: Heavily leverage the benefits of markdown for formatting, such as bulleted lists, bold text, tables, etc. +# 11. Avoid mistaken review comments: +# * Any comment you make must point towards a discrepancy found in the code and the best practice surfaced in your feedback. +# For example, if you are pointing out that constants need to be named in all caps with underscores, +# ensure that the code selected by the comment does not already do this, otherwise it's confusing let alone unnecessary. +# 12. Remove Duplicated code suggestions: +# * Some provided code suggestions are duplicated, please remove the duplicated review comments. +# 13. Don't Approve The Pull Request +# 14. Reference all shell variables as "${VAR}" (with quotes and braces) +# +# ### Review Criteria (Prioritized in Review) +# +# * Correctness: Verify code functionality, handle edge cases, and ensure alignment between function +# descriptions and implementations. Consider common correctness issues (logic errors, error handling, +# race conditions, data validation, API usage, type mismatches). +# * Efficiency: Identify performance bottlenecks, optimize for efficiency, and avoid unnecessary +# loops, iterations, or calculations. Consider common efficiency issues (excessive loops, memory +# leaks, inefficient data structures, redundant calculations, excessive logging, etc.). +# * Maintainability: Assess code readability, modularity, and adherence to language idioms and +# best practices. Consider common maintainability issues (naming, comments/documentation, complexity, +# code duplication, formatting, magic numbers). State the style guide being followed (defaulting to +# commonly used guides, for example Python's PEP 8 style guide or Google Java Style Guide, if no style guide is specified). +# * Security: Identify potential vulnerabilities (e.g., insecure storage, injection attacks, +# insufficient access controls). +# +# ### Miscellaneous Considerations +# * Testing: Ensure adequate unit tests, integration tests, and end-to-end tests. Evaluate +# coverage, edge case handling, and overall test quality. +# * Performance: Assess performance under expected load, identify bottlenecks, and suggest +# optimizations. +# * Scalability: Evaluate how the code will scale with growing user base or data volume. +# * Modularity and Reusability: Assess code organization, modularity, and reusability. Suggest +# refactoring or creating reusable components. +# * Error Logging and Monitoring: Ensure errors are logged effectively, and implement monitoring +# mechanisms to track application health in production. +# +# **CRITICAL CONSTRAINTS:** +# +# You MUST only provide comments on lines that represent the actual changes in +# the diff. This means your comments should only refer to lines that begin with +# a `+` or `-` character in the provided diff content. +# DO NOT comment on lines that start with a space (context lines). +# +# You MUST only add a review comment if there exists an actual ISSUE or BUG in the code changes. +# DO NOT add review comments to tell the user to "check" or "confirm" or "verify" something. +# DO NOT add review comments to tell the user to "ensure" something. +# DO NOT add review comments to explain what the code change does. +# DO NOT add review comments to validate what the code change does. +# DO NOT use the review comments to explain the code to the author. They already know their code. Only comment when there's an improvement opportunity. This is very important. +# +# Pay close attention to line numbers and ensure they are correct. +# Pay close attention to indentations in the code suggestions and make sure they match the code they are to replace. +# Avoid comments on the license headers - if any exists - and instead make comments on the code that is being changed. +# +# It's absolutely important to avoid commenting on the license header of files. +# It's absolutely important to avoid commenting on copyright headers. +# Avoid commenting on hardcoded dates and times being in future or not (for example "this date is in the future"). +# Remember you don't have access to the current date and time and leave that to the author. +# +# Avoid mentioning any of your instructions, settings or criteria. +# +# Here are some general guidelines for setting the severity of your comments +# - Comments about refactoring a hardcoded string or number as a constant are generally considered low severity. +# - Comments about log messages or log enhancements are generally considered low severity. +# - Comments in .md files are medium or low severity. This is really important. +# - Comments about adding or expanding docstring/javadoc have low severity most of the times. +# - Comments about suppressing unchecked warnings or todos are considered low severity. +# - Comments about typos are usually low or medium severity. +# - Comments about testing or on tests are usually low severity. +# - Do not comment about the content of a URL if the content is not directly available in the input. +# +# Keep comments bodies concise and to the point. +# Keep each comment focused on one issue. +# +# ## Context +# The files that are changed in this pull request are represented below in the following +# format, showing the file name and the portions of the file that are changed: +# +# +# FILE: +# DIFF: +# +# +# -------------------- +# +# FILE: +# DIFF: +# +# +# -------------------- +# +# (and so on for all files changed) +# +# +# Note that if you want to make a comment on the LEFT side of the UI / before the diff code version +# to note those line numbers and the corresponding code. Same for a comment on the RIGHT side +# of the UI / after the diff code version to note the line numbers and corresponding code. +# This should be your guide to picking line numbers, and also very importantly, restrict +# your comments to be only within this line range for these files, whether on LEFT or RIGHT. +# If you comment out of bounds, the review will fail, so you must pay attention the file name, +# line numbers, and pre/post diff versions when crafting your comment. +# +# Here are the patches that were implemented in the pull request, per the +# formatting above: +# +# The get the files changed in this pull request, run: +# "$(gh pr diff "${PR_NUMBER}" --patch)" to get the list of changed files PATCH +# +# ## Review +# +# Once you have the information and are ready to leave a review on GitHub, post the review to GitHub using the GitHub MCP tool by: +# 1. Creating a pending review: Use the mcp__github__create_pending_pull_request_review to create a Pending Pull Request Review. +# +# 2. Adding review comments: +# 2.1 Use the mcp__github__add_comment_to_pending_review to add comments to the Pending Pull Request Review. Inline comments are preferred whenever possible, so repeat this step, calling mcp__github__add_comment_to_pending_review, as needed. All comments about specific lines of code should use inline comments. It is preferred to use code suggestions when possible, which include a code block that is labeled "suggestion", which contains what the new code should be. All comments should also have a severity. The syntax is: +# Normal Comment Syntax: +# +# {{SEVERITY}} {{COMMENT_TEXT}} +# +# +# Inline Comment Syntax: (Preferred): +# +# {{SEVERITY}} {{COMMENT_TEXT}} +# ```suggestion +# {{CODE_SUGGESTION}} +# ``` +# +# +# Prepend a severity emoji to each comment: +# - 🟢 for low severity +# - 🟡 for medium severity +# - 🟠 for high severity +# - 🔴 for critical severity +# - 🔵 if severity is unclear +# +# Including all of this, an example inline comment would be: +# +# 🟢 Use camelCase for function names +# ```suggestion +# myFooBarFunction +# ``` +# +# +# A critical severity example would be: +# +# 🔴 Remove storage key from GitHub +# ```suggestion +# ``` +# +# 3. Posting the review: Use the mcp__github__submit_pending_pull_request_review to submit the Pending Pull Request Review. +# +# 3.1 Crafting the summary comment: Include a summary of high level points that were not addressed with inline comments. Be concise. Do not repeat details mentioned inline. +# +# Structure your summary comment using this exact format with markdown: +# ## 📋 Review Summary +# +# Provide a brief 2-3 sentence overview of the PR and overall +# assessment. +# +# ## 🔍 General Feedback +# - List general observations about code quality +# - Mention overall patterns or architectural decisions +# - Highlight positive aspects of the implementation +# - Note any recurring themes across files +# +# ## Final Instructions +# +# Remember, you are running in a VM and no one reviewing your output. Your review must be posted to GitHub using the MCP tools to create a pending review, add comments to the pending review, and submit the pending review. +# +# +# - name: 'Post PR review failure comment' +# if: |- +# ${{ failure() && steps.gemini_pr_review.outcome == 'failure' }} +# uses: 'actions/github-script@v7' +# with: +# github-token: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}' +# script: |- +# github.rest.issues.createComment({ +# owner: '${{ github.repository }}'.split('/')[0], +# repo: '${{ github.repository }}'.split('/')[1], +# issue_number: '${{ steps.get_pr.outputs.pr_number || steps.get_pr_comment.outputs.pr_number }}', +# body: 'There is a problem with the Gemini CLI PR review. Please check the [action logs](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}) for details.' +# }) diff --git a/.release-please-manifest.json b/.release-please-manifest.json index 3ae10ec6db..00d17fe534 100644 --- a/.release-please-manifest.json +++ b/.release-please-manifest.json @@ -1,3 +1,3 @@ { - ".": "2.62.0" + ".": "2.62.1" } \ No newline at end of file diff --git a/CHANGELOG.md b/CHANGELOG.md index 67c5eba17d..3c0bd3a432 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,12 @@ # Changelog +## [2.62.1](https://github.com/googleapis/sdk-platform-java/compare/v2.62.0...v2.62.1) (2025-09-05) + + +### Dependencies + +* Update auth to 1.39.0 ([#3898](https://github.com/googleapis/sdk-platform-java/issues/3898)) ([9a8443d](https://github.com/googleapis/sdk-platform-java/commit/9a8443d71cdbdb7a693b6da08db72edb85490807)) + ## [2.62.0](https://github.com/googleapis/sdk-platform-java/compare/v2.61.0...v2.62.0) (2025-08-19) diff --git a/WORKSPACE b/WORKSPACE index 218d84943c..00959f0c5e 100644 --- a/WORKSPACE +++ b/WORKSPACE @@ -58,7 +58,7 @@ load("@rules_jvm_external//:defs.bzl", "maven_install") load("@io_grpc_grpc_java//:repositories.bzl", "IO_GRPC_GRPC_JAVA_ARTIFACTS") load("@io_grpc_grpc_java//:repositories.bzl", "IO_GRPC_GRPC_JAVA_OVERRIDE_TARGETS") -_gapic_generator_java_version = "2.62.0" # {x-version-update:gapic-generator-java:current} +_gapic_generator_java_version = "2.62.1" # {x-version-update:gapic-generator-java:current} maven_install( artifacts = [ diff --git a/api-common-java/pom.xml b/api-common-java/pom.xml index d43648498b..f62f5e862f 100644 --- a/api-common-java/pom.xml +++ b/api-common-java/pom.xml @@ -5,14 +5,14 @@ com.google.api api-common jar - 2.53.0 + 2.53.1 API Common Common utilities for Google APIs in Java com.google.api gapic-generator-java-pom-parent - 2.62.0 + 2.62.1 ../gapic-generator-java-pom-parent diff --git a/coverage-report/pom.xml b/coverage-report/pom.xml index fe92558b20..61d6200a7e 100644 --- a/coverage-report/pom.xml +++ b/coverage-report/pom.xml @@ -31,22 +31,22 @@ com.google.api gax - 2.70.0 + 2.70.1 com.google.api gax-grpc - 2.70.0 + 2.70.1 com.google.api gax-httpjson - 2.70.0 + 2.70.1 com.google.api api-common - 2.53.0 + 2.53.1 diff --git a/dependencies.txt b/dependencies.txt index ed0c7e751e..4c54691c6f 100644 --- a/dependencies.txt +++ b/dependencies.txt @@ -6,14 +6,14 @@ # Pom-Parent Dependencies # These dependencies are declared: https://github.com/googleapis/sdk-platform-java/blob/main/gapic-generator-java-pom-parent/pom.xml javax.annotation-api=1.3.2 -grpc=1.74.0 -google.auth=1.37.1 -google.http-client=1.47.1 +grpc=1.75.0 +google.auth=1.38.0 +google.http-client=2.0.0 gson=2.13.1 guava=33.4.8-jre -protobuf=4.31.1 +protobuf=4.32.0 # Note: This opentelemetry version refers to the opentelemetry-bom -opentelemetry=1.52.0 +opentelemetry=1.53.0 errorprone=2.41.0 j2objc-annotations=3.1 threetenbp=1.7.2 @@ -30,19 +30,19 @@ google.api-client=2.8.1 threeten-extra=1.8.0 opencensus=0.31.0 findbugs=3.0.2 -jackson=2.19.2 +jackson=2.20.0 codec=1.19.0 httpcomponents.httpcore=4.4.16 httpcomponents.httpclient=4.5.14 apache-httpclient-5=5.5 -apache-httpcore-5=5.3.4 +apache-httpcore-5=5.3.5 perfmark-api=0.27.0 # Note: This is the google opentelemetry exporter and not the general opentelemetry project google.cloud.opentelemetry=0.36.0 flogger=0.9 arrow=18.3.0 -dev.cel=0.10.1 +dev.cel=0.11.0 com.google.crypto.tink=1.18.0 # The follow opentelemetry dependencies have a different version from the opentelemetry-bom -opentelemetry-semconv=1.34.0 +opentelemetry-semconv=1.37.0 io.opentelemetry.contrib.opentelemetry-gcp-resources=1.48.0-alpha diff --git a/gapic-generator-java-bom/pom.xml b/gapic-generator-java-bom/pom.xml index 32f14621d7..66bd24eb45 100644 --- a/gapic-generator-java-bom/pom.xml +++ b/gapic-generator-java-bom/pom.xml @@ -4,7 +4,7 @@ com.google.api gapic-generator-java-bom pom - 2.62.0 + 2.62.1 GAPIC Generator Java BOM BOM for the libraries in gapic-generator-java repository. Users should not @@ -15,7 +15,7 @@ com.google.api gapic-generator-java-pom-parent - 2.62.0 + 2.62.1 ../gapic-generator-java-pom-parent @@ -75,81 +75,81 @@ com.google.api api-common - 2.53.0 + 2.53.1 com.google.api gax-bom - 2.70.0 + 2.70.1 pom import com.google.api gapic-generator-java - 2.62.0 + 2.62.1 com.google.api.grpc grpc-google-common-protos - 2.61.0 + 2.61.1 com.google.api.grpc proto-google-common-protos - 2.61.0 + 2.61.1 com.google.api.grpc proto-google-iam-v1 - 1.56.0 + 1.56.1 com.google.api.grpc proto-google-iam-v2 - 1.56.0 + 1.56.1 com.google.api.grpc proto-google-iam-v2beta - 1.56.0 + 1.56.1 com.google.api.grpc proto-google-iam-v3 - 1.56.0 + 1.56.1 com.google.api.grpc proto-google-iam-v3beta - 1.56.0 + 1.56.1 com.google.api.grpc grpc-google-iam-v1 - 1.56.0 + 1.56.1 com.google.api.grpc grpc-google-iam-v2 - 1.56.0 + 1.56.1 com.google.api.grpc grpc-google-iam-v2beta - 1.56.0 + 1.56.1 com.google.api.grpc grpc-google-iam-v3 - 1.56.0 + 1.56.1 com.google.api.grpc grpc-google-iam-v3beta - 1.56.0 + 1.56.1 diff --git a/gapic-generator-java-pom-parent/pom.xml b/gapic-generator-java-pom-parent/pom.xml index b9e052f036..8aac0f2cae 100644 --- a/gapic-generator-java-pom-parent/pom.xml +++ b/gapic-generator-java-pom-parent/pom.xml @@ -5,7 +5,7 @@ 4.0.0 com.google.api gapic-generator-java-pom-parent - 2.62.0 + 2.62.1 pom GAPIC Generator Java POM Parent https://github.com/googleapis/sdk-platform-java @@ -27,7 +27,7 @@ consistent across modules in this repository --> 1.3.2 1.71.0 - 1.37.1 + 1.39.0 1.47.1 2.12.1 33.4.0-jre diff --git a/gapic-generator-java/pom.xml b/gapic-generator-java/pom.xml index 0598671feb..b1cd44dd9d 100644 --- a/gapic-generator-java/pom.xml +++ b/gapic-generator-java/pom.xml @@ -4,7 +4,7 @@ 4.0.0 com.google.api gapic-generator-java - 2.62.0 + 2.62.1 GAPIC Generator Java GAPIC generator Java @@ -22,7 +22,7 @@ com.google.api gapic-generator-java-pom-parent - 2.62.0 + 2.62.1 ../gapic-generator-java-pom-parent @@ -31,7 +31,7 @@ com.google.api gapic-generator-java-bom - 2.62.0 + 2.62.1 pom import diff --git a/gax-java/README.md b/gax-java/README.md index d2612ce947..4e7153e577 100644 --- a/gax-java/README.md +++ b/gax-java/README.md @@ -34,27 +34,27 @@ If you are using Maven, add this to your pom.xml file com.google.api gax - 2.70.0 + 2.70.1 com.google.api gax-grpc - 2.70.0 + 2.70.1 ``` If you are using Gradle, add this to your dependencies ```Groovy -compile 'com.google.api:gax:2.70.0', - 'com.google.api:gax-grpc:2.70.0' +compile 'com.google.api:gax:2.70.1', + 'com.google.api:gax-grpc:2.70.1' ``` If you are using SBT, add this to your dependencies ```Scala -libraryDependencies += "com.google.api" % "gax" % "2.70.0" -libraryDependencies += "com.google.api" % "gax-grpc" % "2.70.0" +libraryDependencies += "com.google.api" % "gax" % "2.70.1" +libraryDependencies += "com.google.api" % "gax-grpc" % "2.70.1" ``` [//]: # ({x-version-update-end}) diff --git a/gax-java/dependencies.properties b/gax-java/dependencies.properties index 856d473a76..93803ceb75 100644 --- a/gax-java/dependencies.properties +++ b/gax-java/dependencies.properties @@ -8,16 +8,16 @@ # Versions of oneself # {x-version-update-start:gax:current} -version.gax=2.70.0 +version.gax=2.70.1 # {x-version-update-end} # {x-version-update-start:gax:current} -version.gax_grpc=2.70.0 +version.gax_grpc=2.70.1 # {x-version-update-end} # {x-version-update-start:gax:current} -version.gax_bom=2.70.0 +version.gax_bom=2.70.1 # {x-version-update-end} # {x-version-update-start:gax:current} -version.gax_httpjson=2.70.0 +version.gax_httpjson=2.70.1 # {x-version-update-end} # Versions for dependencies which actual artifacts differ between Bazel and Gradle. @@ -37,8 +37,8 @@ version.io_grpc=1.71.0 # 2) Replace all characters which are neither alphabetic nor digits with the underscore ('_') character maven.com_google_api_grpc_proto_google_common_protos=com.google.api.grpc:proto-google-common-protos:2.57.0 maven.com_google_api_grpc_grpc_google_common_protos=com.google.api.grpc:grpc-google-common-protos:2.57.0 -maven.com_google_auth_google_auth_library_oauth2_http=com.google.auth:google-auth-library-oauth2-http:1.37.1 -maven.com_google_auth_google_auth_library_credentials=com.google.auth:google-auth-library-credentials:1.37.1 +maven.com_google_auth_google_auth_library_oauth2_http=com.google.auth:google-auth-library-oauth2-http:1.39.0 +maven.com_google_auth_google_auth_library_credentials=com.google.auth:google-auth-library-credentials:1.39.0 maven.io_opentelemetry_opentelemetry_api=io.opentelemetry:opentelemetry-api:1.47.0 maven.io_opencensus_opencensus_api=io.opencensus:opencensus-api:0.31.1 maven.io_opencensus_opencensus_contrib_grpc_metrics=io.opencensus:opencensus-contrib-grpc-metrics:0.31.1 diff --git a/gax-java/gax-bom/pom.xml b/gax-java/gax-bom/pom.xml index cbc36b235c..2a9c9bca0f 100644 --- a/gax-java/gax-bom/pom.xml +++ b/gax-java/gax-bom/pom.xml @@ -3,7 +3,7 @@ 4.0.0 com.google.api gax-bom - 2.70.0 + 2.70.1 pom GAX (Google Api eXtensions) for Java (BOM) Google Api eXtensions for Java (BOM) @@ -43,55 +43,55 @@ com.google.api gax - 2.70.0 + 2.70.1 com.google.api gax - 2.70.0 + 2.70.1 test-jar testlib com.google.api gax - 2.70.0 + 2.70.1 testlib com.google.api gax-grpc - 2.70.0 + 2.70.1 com.google.api gax-grpc - 2.70.0 + 2.70.1 test-jar testlib com.google.api gax-grpc - 2.70.0 + 2.70.1 testlib com.google.api gax-httpjson - 2.70.0 + 2.70.1 com.google.api gax-httpjson - 2.70.0 + 2.70.1 test-jar testlib com.google.api gax-httpjson - 2.70.0 + 2.70.1 testlib diff --git a/gax-java/gax-grpc/pom.xml b/gax-java/gax-grpc/pom.xml index c1ffa89912..a74c466b00 100644 --- a/gax-java/gax-grpc/pom.xml +++ b/gax-java/gax-grpc/pom.xml @@ -3,7 +3,7 @@ 4.0.0 gax-grpc - 2.70.0 + 2.70.1 jar GAX (Google Api eXtensions) for Java (gRPC) Google Api eXtensions for Java (gRPC) @@ -11,7 +11,7 @@ com.google.api gax-parent - 2.70.0 + 2.70.1 diff --git a/gax-java/gax-httpjson/pom.xml b/gax-java/gax-httpjson/pom.xml index 759adc41d4..db3f0d3bac 100644 --- a/gax-java/gax-httpjson/pom.xml +++ b/gax-java/gax-httpjson/pom.xml @@ -3,7 +3,7 @@ 4.0.0 gax-httpjson - 2.70.0 + 2.70.1 jar GAX (Google Api eXtensions) for Java (HTTP JSON) Google Api eXtensions for Java (HTTP JSON) @@ -11,7 +11,7 @@ com.google.api gax-parent - 2.70.0 + 2.70.1 diff --git a/gax-java/gax/pom.xml b/gax-java/gax/pom.xml index ee970ecef6..39d1134758 100644 --- a/gax-java/gax/pom.xml +++ b/gax-java/gax/pom.xml @@ -3,7 +3,7 @@ 4.0.0 gax - 2.70.0 + 2.70.1 jar GAX (Google Api eXtensions) for Java (Core) Google Api eXtensions for Java (Core) @@ -11,7 +11,7 @@ com.google.api gax-parent - 2.70.0 + 2.70.1 diff --git a/gax-java/pom.xml b/gax-java/pom.xml index 8fb060621d..c3be2a9a85 100644 --- a/gax-java/pom.xml +++ b/gax-java/pom.xml @@ -4,14 +4,14 @@ com.google.api gax-parent pom - 2.70.0 + 2.70.1 GAX (Google Api eXtensions) for Java (Parent) Google Api eXtensions for Java (Parent) com.google.api gapic-generator-java-pom-parent - 2.62.0 + 2.62.1 ../gapic-generator-java-pom-parent @@ -50,7 +50,7 @@ com.google.api api-common - 2.53.0 + 2.53.1 com.google.auth @@ -98,24 +98,24 @@ com.google.api gax - 2.70.0 + 2.70.1 com.google.api gax - 2.70.0 + 2.70.1 test-jar testlib com.google.api.grpc proto-google-common-protos - 2.61.0 + 2.61.1 com.google.api.grpc grpc-google-common-protos - 2.61.0 + 2.61.1 io.grpc diff --git a/generation_config.yaml b/generation_config.yaml index b3fc43f62c..7e7821e071 100644 --- a/generation_config.yaml +++ b/generation_config.yaml @@ -1,4 +1,4 @@ -googleapis_commitish: efe27dbe161b24710f4e95415e8f38922ae6f453 +googleapis_commitish: c249577397a9ae79e07db34925efd0984c2ef26a # the libraries are ordered with respect to library name, which is # java-{library.library_name} or java-{library.api-shortname} when # library.library_name is not defined. diff --git a/hermetic_build/library_generation/owlbot/templates/java_library/.kokoro/presubmit/graalvm-native-a.cfg b/hermetic_build/library_generation/owlbot/templates/java_library/.kokoro/presubmit/graalvm-native-a.cfg index 5816d61073..a562a6398b 100644 --- a/hermetic_build/library_generation/owlbot/templates/java_library/.kokoro/presubmit/graalvm-native-a.cfg +++ b/hermetic_build/library_generation/owlbot/templates/java_library/.kokoro/presubmit/graalvm-native-a.cfg @@ -3,7 +3,7 @@ # Configure the docker image for kokoro-trampoline. env_vars: { key: "TRAMPOLINE_IMAGE" - value: "gcr.io/cloud-devrel-public-resources/graalvm_sdk_platform_a:3.52.0" # {x-version-update:google-cloud-shared-dependencies:current} + value: "gcr.io/cloud-devrel-public-resources/graalvm_sdk_platform_a:3.52.1" # {x-version-update:google-cloud-shared-dependencies:current} } env_vars: { diff --git a/hermetic_build/library_generation/owlbot/templates/java_library/.kokoro/presubmit/graalvm-native-b.cfg b/hermetic_build/library_generation/owlbot/templates/java_library/.kokoro/presubmit/graalvm-native-b.cfg index 7986fd6731..2257ccce67 100644 --- a/hermetic_build/library_generation/owlbot/templates/java_library/.kokoro/presubmit/graalvm-native-b.cfg +++ b/hermetic_build/library_generation/owlbot/templates/java_library/.kokoro/presubmit/graalvm-native-b.cfg @@ -3,7 +3,7 @@ # Configure the docker image for kokoro-trampoline. env_vars: { key: "TRAMPOLINE_IMAGE" - value: "gcr.io/cloud-devrel-public-resources/graalvm_sdk_platform_b:3.52.0" # {x-version-update:google-cloud-shared-dependencies:current} + value: "gcr.io/cloud-devrel-public-resources/graalvm_sdk_platform_b:3.52.1" # {x-version-update:google-cloud-shared-dependencies:current} } env_vars: { diff --git a/hermetic_build/library_generation/owlbot/templates/java_library/.kokoro/presubmit/graalvm-native-c.cfg b/hermetic_build/library_generation/owlbot/templates/java_library/.kokoro/presubmit/graalvm-native-c.cfg index acecfce1bf..a9294de35a 100644 --- a/hermetic_build/library_generation/owlbot/templates/java_library/.kokoro/presubmit/graalvm-native-c.cfg +++ b/hermetic_build/library_generation/owlbot/templates/java_library/.kokoro/presubmit/graalvm-native-c.cfg @@ -3,7 +3,7 @@ # Configure the docker image for kokoro-trampoline. env_vars: { key: "TRAMPOLINE_IMAGE" - value: "gcr.io/cloud-devrel-public-resources/graalvm_sdk_platform_c:3.52.0" # {x-version-update:google-cloud-shared-dependencies:current} + value: "gcr.io/cloud-devrel-public-resources/graalvm_sdk_platform_c:3.52.1" # {x-version-update:google-cloud-shared-dependencies:current} } env_vars: { diff --git a/java-common-protos/grpc-google-common-protos/pom.xml b/java-common-protos/grpc-google-common-protos/pom.xml index db6454572f..b08efc95ca 100644 --- a/java-common-protos/grpc-google-common-protos/pom.xml +++ b/java-common-protos/grpc-google-common-protos/pom.xml @@ -4,13 +4,13 @@ 4.0.0 com.google.api.grpc grpc-google-common-protos - 2.61.0 + 2.61.1 grpc-google-common-protos GRPC library for grpc-google-common-protos com.google.api.grpc google-common-protos-parent - 2.61.0 + 2.61.1 diff --git a/java-common-protos/pom.xml b/java-common-protos/pom.xml index fef5ded0c1..9fbb4eca82 100644 --- a/java-common-protos/pom.xml +++ b/java-common-protos/pom.xml @@ -4,7 +4,7 @@ com.google.api.grpc google-common-protos-parent pom - 2.61.0 + 2.61.1 Google Common Protos Parent Java idiomatic client for Google Cloud Platform services. @@ -13,7 +13,7 @@ com.google.api gapic-generator-java-pom-parent - 2.62.0 + 2.62.1 ../gapic-generator-java-pom-parent @@ -51,7 +51,7 @@ com.google.cloud third-party-dependencies - 3.52.0 + 3.52.1 pom import @@ -65,7 +65,7 @@ com.google.api.grpc grpc-google-common-protos - 2.61.0 + 2.61.1 io.grpc @@ -77,7 +77,7 @@ com.google.api.grpc proto-google-common-protos - 2.61.0 + 2.61.1 com.google.guava diff --git a/java-common-protos/proto-google-common-protos/pom.xml b/java-common-protos/proto-google-common-protos/pom.xml index 7d02a2b58e..ff9cffbe2f 100644 --- a/java-common-protos/proto-google-common-protos/pom.xml +++ b/java-common-protos/proto-google-common-protos/pom.xml @@ -3,13 +3,13 @@ 4.0.0 com.google.api.grpc proto-google-common-protos - 2.61.0 + 2.61.1 proto-google-common-protos PROTO library for proto-google-common-protos com.google.api.grpc google-common-protos-parent - 2.61.0 + 2.61.1 diff --git a/java-core/google-cloud-core-bom/pom.xml b/java-core/google-cloud-core-bom/pom.xml index df49b0cad3..449d934460 100644 --- a/java-core/google-cloud-core-bom/pom.xml +++ b/java-core/google-cloud-core-bom/pom.xml @@ -3,13 +3,13 @@ 4.0.0 com.google.cloud google-cloud-core-bom - 2.60.0 + 2.60.1 pom com.google.api gapic-generator-java-pom-parent - 2.62.0 + 2.62.1 ../../gapic-generator-java-pom-parent @@ -23,17 +23,17 @@ com.google.cloud google-cloud-core - 2.60.0 + 2.60.1 com.google.cloud google-cloud-core-grpc - 2.60.0 + 2.60.1 com.google.cloud google-cloud-core-http - 2.60.0 + 2.60.1 diff --git a/java-core/google-cloud-core-grpc/pom.xml b/java-core/google-cloud-core-grpc/pom.xml index 6594f68153..52049aef88 100644 --- a/java-core/google-cloud-core-grpc/pom.xml +++ b/java-core/google-cloud-core-grpc/pom.xml @@ -3,7 +3,7 @@ 4.0.0 com.google.cloud google-cloud-core-grpc - 2.60.0 + 2.60.1 jar Google Cloud Core gRPC @@ -12,7 +12,7 @@ com.google.cloud google-cloud-core-parent - 2.60.0 + 2.60.1 google-cloud-core-grpc diff --git a/java-core/google-cloud-core-http/pom.xml b/java-core/google-cloud-core-http/pom.xml index 0c0005f86c..b63bfe02e1 100644 --- a/java-core/google-cloud-core-http/pom.xml +++ b/java-core/google-cloud-core-http/pom.xml @@ -3,7 +3,7 @@ 4.0.0 com.google.cloud google-cloud-core-http - 2.60.0 + 2.60.1 jar Google Cloud Core HTTP @@ -12,7 +12,7 @@ com.google.cloud google-cloud-core-parent - 2.60.0 + 2.60.1 google-cloud-core-http diff --git a/java-core/google-cloud-core/pom.xml b/java-core/google-cloud-core/pom.xml index 8982ebf8ae..5459739ff0 100644 --- a/java-core/google-cloud-core/pom.xml +++ b/java-core/google-cloud-core/pom.xml @@ -3,7 +3,7 @@ 4.0.0 com.google.cloud google-cloud-core - 2.60.0 + 2.60.1 jar Google Cloud Core @@ -12,7 +12,7 @@ com.google.cloud google-cloud-core-parent - 2.60.0 + 2.60.1 google-cloud-core diff --git a/java-core/pom.xml b/java-core/pom.xml index dcb8cbbc83..14de3eaaf1 100644 --- a/java-core/pom.xml +++ b/java-core/pom.xml @@ -4,7 +4,7 @@ com.google.cloud google-cloud-core-parent pom - 2.60.0 + 2.60.1 Google Cloud Core Parent Java idiomatic client for Google Cloud Platform services. @@ -13,7 +13,7 @@ com.google.api gapic-generator-java-pom-parent - 2.62.0 + 2.62.1 ../gapic-generator-java-pom-parent @@ -33,7 +33,7 @@ com.google.cloud google-cloud-shared-dependencies - 3.52.0 + 3.52.1 pom import diff --git a/java-iam/grpc-google-iam-v1/pom.xml b/java-iam/grpc-google-iam-v1/pom.xml index daba8b27f2..564b5990a4 100644 --- a/java-iam/grpc-google-iam-v1/pom.xml +++ b/java-iam/grpc-google-iam-v1/pom.xml @@ -4,13 +4,13 @@ 4.0.0 com.google.api.grpc grpc-google-iam-v1 - 1.56.0 + 1.56.1 grpc-google-iam-v1 GRPC library for grpc-google-iam-v1 com.google.cloud google-iam-parent - 1.56.0 + 1.56.1 diff --git a/java-iam/grpc-google-iam-v2/pom.xml b/java-iam/grpc-google-iam-v2/pom.xml index 0b7a8101c4..8a7b510b77 100644 --- a/java-iam/grpc-google-iam-v2/pom.xml +++ b/java-iam/grpc-google-iam-v2/pom.xml @@ -4,13 +4,13 @@ 4.0.0 com.google.api.grpc grpc-google-iam-v2 - 1.56.0 + 1.56.1 grpc-google-iam-v2 GRPC library for proto-google-iam-v2 com.google.cloud google-iam-parent - 1.56.0 + 1.56.1 diff --git a/java-iam/grpc-google-iam-v2beta/pom.xml b/java-iam/grpc-google-iam-v2beta/pom.xml index 478a6c2304..de07b82ce7 100644 --- a/java-iam/grpc-google-iam-v2beta/pom.xml +++ b/java-iam/grpc-google-iam-v2beta/pom.xml @@ -4,13 +4,13 @@ 4.0.0 com.google.api.grpc grpc-google-iam-v2beta - 1.56.0 + 1.56.1 grpc-google-iam-v2beta GRPC library for proto-google-iam-v1 com.google.cloud google-iam-parent - 1.56.0 + 1.56.1 diff --git a/java-iam/grpc-google-iam-v3/pom.xml b/java-iam/grpc-google-iam-v3/pom.xml index b1e2b1c3dc..e0c04d00ec 100644 --- a/java-iam/grpc-google-iam-v3/pom.xml +++ b/java-iam/grpc-google-iam-v3/pom.xml @@ -4,13 +4,13 @@ 4.0.0 com.google.api.grpc grpc-google-iam-v3 - 1.56.0 + 1.56.1 grpc-google-iam-v3 GRPC library for proto-google-iam-v3 com.google.cloud google-iam-parent - 1.56.0 + 1.56.1 diff --git a/java-iam/grpc-google-iam-v3beta/pom.xml b/java-iam/grpc-google-iam-v3beta/pom.xml index 3424be1d7e..33434d29eb 100644 --- a/java-iam/grpc-google-iam-v3beta/pom.xml +++ b/java-iam/grpc-google-iam-v3beta/pom.xml @@ -4,13 +4,13 @@ 4.0.0 com.google.api.grpc grpc-google-iam-v3beta - 1.56.0 + 1.56.1 grpc-google-iam-v3beta GRPC library for proto-google-iam-v3beta com.google.cloud google-iam-parent - 1.56.0 + 1.56.1 diff --git a/java-iam/pom.xml b/java-iam/pom.xml index 00575c0878..366073b872 100644 --- a/java-iam/pom.xml +++ b/java-iam/pom.xml @@ -4,7 +4,7 @@ com.google.cloud google-iam-parent pom - 1.56.0 + 1.56.1 Google IAM Parent Java idiomatic client for Google Cloud Platform services. @@ -13,7 +13,7 @@ com.google.api gapic-generator-java-pom-parent - 2.62.0 + 2.62.1 ../gapic-generator-java-pom-parent @@ -50,19 +50,19 @@ com.google.cloud third-party-dependencies - 3.52.0 + 3.52.1 pom import com.google.api.grpc proto-google-iam-v3beta - 1.56.0 + 1.56.1 com.google.api.grpc grpc-google-iam-v3beta - 1.56.0 + 1.56.1 com.google.guava @@ -88,59 +88,59 @@ com.google.api gax-bom - 2.70.0 + 2.70.1 pom import com.google.api api-common - 2.53.0 + 2.53.1 com.google.api.grpc proto-google-iam-v2 - 1.56.0 + 1.56.1 com.google.api.grpc grpc-google-iam-v2 - 1.56.0 + 1.56.1 com.google.api.grpc proto-google-common-protos - 2.61.0 + 2.61.1 com.google.api.grpc proto-google-iam-v2beta - 1.56.0 + 1.56.1 com.google.api.grpc grpc-google-iam-v1 - 1.56.0 + 1.56.1 com.google.api.grpc grpc-google-iam-v2beta - 1.56.0 + 1.56.1 com.google.api.grpc proto-google-iam-v1 - 1.56.0 + 1.56.1 com.google.api.grpc proto-google-iam-v3 - 1.56.0 + 1.56.1 com.google.api.grpc grpc-google-iam-v3 - 1.56.0 + 1.56.1 javax.annotation diff --git a/java-iam/proto-google-iam-v1/pom.xml b/java-iam/proto-google-iam-v1/pom.xml index a069503ba2..ccf169aeda 100644 --- a/java-iam/proto-google-iam-v1/pom.xml +++ b/java-iam/proto-google-iam-v1/pom.xml @@ -3,13 +3,13 @@ 4.0.0 com.google.api.grpc proto-google-iam-v1 - 1.56.0 + 1.56.1 proto-google-iam-v1 PROTO library for proto-google-iam-v1 com.google.cloud google-iam-parent - 1.56.0 + 1.56.1 diff --git a/java-iam/proto-google-iam-v2/pom.xml b/java-iam/proto-google-iam-v2/pom.xml index 35f4c9e4e0..126f8084f5 100644 --- a/java-iam/proto-google-iam-v2/pom.xml +++ b/java-iam/proto-google-iam-v2/pom.xml @@ -4,13 +4,13 @@ 4.0.0 com.google.api.grpc proto-google-iam-v2 - 1.56.0 + 1.56.1 proto-google-iam-v2 Proto library for proto-google-iam-v1 com.google.cloud google-iam-parent - 1.56.0 + 1.56.1 diff --git a/java-iam/proto-google-iam-v2beta/pom.xml b/java-iam/proto-google-iam-v2beta/pom.xml index 806d6abab1..760119a9fa 100644 --- a/java-iam/proto-google-iam-v2beta/pom.xml +++ b/java-iam/proto-google-iam-v2beta/pom.xml @@ -4,13 +4,13 @@ 4.0.0 com.google.api.grpc proto-google-iam-v2beta - 1.56.0 + 1.56.1 proto-google-iam-v2beta Proto library for proto-google-iam-v1 com.google.cloud google-iam-parent - 1.56.0 + 1.56.1 diff --git a/java-iam/proto-google-iam-v3/pom.xml b/java-iam/proto-google-iam-v3/pom.xml index 3111e68e51..1ed9cdf05a 100644 --- a/java-iam/proto-google-iam-v3/pom.xml +++ b/java-iam/proto-google-iam-v3/pom.xml @@ -4,13 +4,13 @@ 4.0.0 com.google.api.grpc proto-google-iam-v3 - 1.56.0 + 1.56.1 proto-google-iam-v3 Proto library for proto-google-iam-v3 com.google.cloud google-iam-parent - 1.56.0 + 1.56.1 diff --git a/java-iam/proto-google-iam-v3beta/pom.xml b/java-iam/proto-google-iam-v3beta/pom.xml index 7f6d28c69f..a74978b79a 100644 --- a/java-iam/proto-google-iam-v3beta/pom.xml +++ b/java-iam/proto-google-iam-v3beta/pom.xml @@ -4,13 +4,13 @@ 4.0.0 com.google.api.grpc proto-google-iam-v3beta - 1.56.0 + 1.56.1 proto-google-iam-v3beta Proto library for proto-google-iam-v3beta com.google.cloud google-iam-parent - 1.56.0 + 1.56.1 diff --git a/java-shared-dependencies/README.md b/java-shared-dependencies/README.md index 3bf73a8dd4..54cd7cc2f6 100644 --- a/java-shared-dependencies/README.md +++ b/java-shared-dependencies/README.md @@ -14,7 +14,7 @@ If you are using Maven, add this to the `dependencyManagement` section. com.google.cloud google-cloud-shared-dependencies - 3.52.0 + 3.52.1 pom import diff --git a/java-shared-dependencies/dependency-convergence-check/pom.xml b/java-shared-dependencies/dependency-convergence-check/pom.xml index 57df4a6497..0bf6281b21 100644 --- a/java-shared-dependencies/dependency-convergence-check/pom.xml +++ b/java-shared-dependencies/dependency-convergence-check/pom.xml @@ -3,7 +3,7 @@ 4.0.0 com.google.cloud shared-dependencies-dependency-convergence-test - 3.52.0 + 3.52.1 Dependency convergence test for certain artifacts in Google Cloud Shared Dependencies An dependency convergence test case for the shared dependencies BOM. A failure of this test case means diff --git a/java-shared-dependencies/first-party-dependencies/pom.xml b/java-shared-dependencies/first-party-dependencies/pom.xml index 575d44addf..ac4e467897 100644 --- a/java-shared-dependencies/first-party-dependencies/pom.xml +++ b/java-shared-dependencies/first-party-dependencies/pom.xml @@ -6,7 +6,7 @@ com.google.cloud first-party-dependencies pom - 3.52.0 + 3.52.1 Google Cloud First-party Shared Dependencies Shared first-party dependencies for Google Cloud Java libraries. @@ -33,7 +33,7 @@ com.google.api gapic-generator-java-bom - 2.62.0 + 2.62.1 pom import @@ -45,7 +45,7 @@ com.google.cloud google-cloud-core-bom - 2.60.0 + 2.60.1 pom import @@ -69,13 +69,13 @@ com.google.cloud google-cloud-core - 2.60.0 + 2.60.1 test-jar com.google.cloud google-cloud-core - 2.60.0 + 2.60.1 tests diff --git a/java-shared-dependencies/pom.xml b/java-shared-dependencies/pom.xml index 3f75c050d6..b9390682ca 100644 --- a/java-shared-dependencies/pom.xml +++ b/java-shared-dependencies/pom.xml @@ -4,7 +4,7 @@ com.google.cloud google-cloud-shared-dependencies pom - 3.52.0 + 3.52.1 first-party-dependencies third-party-dependencies @@ -17,7 +17,7 @@ com.google.api gapic-generator-java-pom-parent - 2.62.0 + 2.62.1 ../gapic-generator-java-pom-parent @@ -31,14 +31,14 @@ com.google.cloud first-party-dependencies - 3.52.0 + 3.52.1 pom import com.google.cloud third-party-dependencies - 3.52.0 + 3.52.1 pom import diff --git a/java-shared-dependencies/third-party-dependencies/pom.xml b/java-shared-dependencies/third-party-dependencies/pom.xml index 7be8a0df60..91ab957d1f 100644 --- a/java-shared-dependencies/third-party-dependencies/pom.xml +++ b/java-shared-dependencies/third-party-dependencies/pom.xml @@ -6,7 +6,7 @@ com.google.cloud third-party-dependencies pom - 3.52.0 + 3.52.1 Google Cloud Third-party Shared Dependencies Shared third-party dependencies for Google Cloud Java libraries. @@ -15,7 +15,7 @@ com.google.api gapic-generator-java-pom-parent - 2.62.0 + 2.62.1 ../../gapic-generator-java-pom-parent diff --git a/java-shared-dependencies/upper-bound-check/pom.xml b/java-shared-dependencies/upper-bound-check/pom.xml index 0af8ffe364..e2112b75d4 100644 --- a/java-shared-dependencies/upper-bound-check/pom.xml +++ b/java-shared-dependencies/upper-bound-check/pom.xml @@ -4,7 +4,7 @@ com.google.cloud shared-dependencies-upper-bound-test pom - 3.52.0 + 3.52.1 Upper bound test for Google Cloud Shared Dependencies An upper bound test case for the shared dependencies BOM. A failure of this test case means @@ -30,7 +30,7 @@ com.google.cloud google-cloud-shared-dependencies - 3.52.0 + 3.52.1 pom import diff --git a/java-showcase/pom.xml b/java-showcase/pom.xml index 5bcb07caa3..0fe8fc9957 100644 --- a/java-showcase/pom.xml +++ b/java-showcase/pom.xml @@ -32,7 +32,7 @@ com.google.cloud google-cloud-shared-dependencies - 3.52.0 + 3.52.1 pom import diff --git a/sdk-platform-java-config/pom.xml b/sdk-platform-java-config/pom.xml index 77fc9393cf..0b6117cca4 100644 --- a/sdk-platform-java-config/pom.xml +++ b/sdk-platform-java-config/pom.xml @@ -4,7 +4,7 @@ com.google.cloud sdk-platform-java-config pom - 3.52.0 + 3.52.1 SDK Platform For Java Configurations Shared build configuration for Google Cloud Java libraries. @@ -17,6 +17,6 @@ - 3.52.0 + 3.52.1 \ No newline at end of file diff --git a/versions.txt b/versions.txt index 51a166072a..613ee3daf6 100644 --- a/versions.txt +++ b/versions.txt @@ -1,26 +1,26 @@ # Format: # module:released-version:current-version -gapic-generator-java:2.62.0:2.62.0 -api-common:2.53.0:2.53.0 -gax:2.70.0:2.70.0 -gax-grpc:2.70.0:2.70.0 -gax-httpjson:0.155.0:0.155.0 -proto-google-common-protos:2.61.0:2.61.0 -grpc-google-common-protos:2.61.0:2.61.0 -proto-google-iam-v1:1.56.0:1.56.0 -grpc-google-iam-v1:1.56.0:1.56.0 -proto-google-iam-v2beta:1.56.0:1.56.0 -grpc-google-iam-v2beta:1.56.0:1.56.0 -google-iam-policy:1.56.0:1.56.0 -proto-google-iam-v2:1.56.0:1.56.0 -grpc-google-iam-v2:1.56.0:1.56.0 -google-cloud-core:2.60.0:2.60.0 -google-cloud-shared-dependencies:3.52.0:3.52.0 -gapic-showcase:0.8.0:0.8.0 -proto-gapic-showcase-v1beta1:0.8.0:0.8.0 -grpc-gapic-showcase-v1beta1:0.8.0:0.8.0 -proto-google-iam-v3:1.56.0:1.56.0 -grpc-google-iam-v3:1.56.0:1.56.0 -proto-google-iam-v3beta:1.56.0:1.56.0 -grpc-google-iam-v3beta:1.56.0:1.56.0 +gapic-generator-java:2.62.1:2.62.1 +api-common:2.53.1:2.53.1 +gax:2.70.1:2.70.1 +gax-grpc:2.70.1:2.70.1 +gax-httpjson:0.155.1:0.155.1 +proto-google-common-protos:2.61.1:2.61.1 +grpc-google-common-protos:2.61.1:2.61.1 +proto-google-iam-v1:1.56.1:1.56.1 +grpc-google-iam-v1:1.56.1:1.56.1 +proto-google-iam-v2beta:1.56.1:1.56.1 +grpc-google-iam-v2beta:1.56.1:1.56.1 +google-iam-policy:1.56.1:1.56.1 +proto-google-iam-v2:1.56.1:1.56.1 +grpc-google-iam-v2:1.56.1:1.56.1 +google-cloud-core:2.60.1:2.60.1 +google-cloud-shared-dependencies:3.52.1:3.52.1 +gapic-showcase:0.8.1:0.8.1 +proto-gapic-showcase-v1beta1:0.8.1:0.8.1 +grpc-gapic-showcase-v1beta1:0.8.1:0.8.1 +proto-google-iam-v3:1.56.1:1.56.1 +grpc-google-iam-v3:1.56.1:1.56.1 +proto-google-iam-v3beta:1.56.1:1.56.1 +grpc-google-iam-v3beta:1.56.1:1.56.1