Bumping packages to latest stable versions

[distroless-bot]

Bumping non-snapshot packages to latest stable version

true

[gemini-code-assist]

Summary of Changes

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

This pull request systematically updates a wide array of non-snapshot packages to their latest stable versions across Debian Bookworm and Trixie distributions, as well as Adoptium Java runtimes. The primary goal is to enhance the stability, security, and maintainability of the project by incorporating the most recent upstream fixes and features for critical dependencies.

Highlights

• Adoptium Java Runtime Updates: Temurin 21 JDK/JRE and Temurin 25 JDK/JRE packages for the ppc64el architecture have been updated to their latest stable versions, specifically from 21.0.8.0.0+9-0 to 21.0.9.0.0+10-0 and 25.0.0.0.0+36-0 to 25.0.1.0.0+8-0 respectively.
• Debian Bookworm Package Bumps: Numerous core packages for Debian Bookworm, including libc-bin, libc6, libssl3, openssl, tzdata, and various gcc and libstdc++ components, have been updated to their latest stable releases.
• Debian Trixie Package Bumps: Key packages for Debian Trixie, such as libc-bin, libc6, libssl3t64, openssl, tzdata, zlib1g, and gcc components, have been updated to their latest stable releases.
• Python-related Package Updates (Bookworm): Several Python-related dependencies for Bookworm, including libpython3.11-minimal, libpython3.11-stdlib, and python3.11-minimal, have been updated.
• Bazel Lock File Update: The MODULE.bazel.lock file has been updated to reflect the new package versions and their corresponding SHA256 digests across all affected distributions and architectures.

Using Gemini Code Assist

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

Invoking Gemini

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

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

Customization

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

Limitations & Feedback

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

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

Footnotes

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

[github-actions]

🌳 🔧 Config Check

This pull request has not modified the root BUILD

[gemini-code-assist]

Code Review

This pull request updates several package versions in the MODULE.bazel.lock and private/repos/deb/trixie_adoptium.lock.json files. The changes appear to be routine dependency updates, bringing package versions for the ppc64el architecture in line with other architectures. The modifications in both files are consistent with each other. I have reviewed the changes and they seem correct. There are no issues to report.

[github-actions]

🌳 🔄 Image Check

This pull request has modified the following images:

//java:java_base_root_amd64_debian12
//java:java_base_nonroot_amd64_debian12
//java:java_base_debug_root_amd64_debian12
//java:java_base_debug_nonroot_amd64_debian12
//java:java_base_debug_root_arm64_debian12
//java:java_base_root_s390x_debian12
//java:java_base_root_amd64_debian12
//java:java_base_nonroot_arm64_debian12
//java:java_base_debug_nonroot_s390x_debian12
//java:java_base_debug_root_s390x_debian12
//java:java_base_nonroot_amd64_debian12
//java:java_base_debug_root_amd64_debian12
//java:java17_debug_root_amd64_debian12
//java:java_base_debug_nonroot_amd64_debian12
//java:java17_debug_root_ppc64le_debian12
//java:java17_nonroot_arm64_debian12
//java:java_base_nonroot_ppc64le_debian12
//java:java17_root_ppc64le_debian12
//java:java17_root_amd64_debian12
//java:java_base_debug_nonroot_arm64_debian12
//java:java17_nonroot_amd64_debian12
//java:java17_debug_root_amd64_debian12
//java:java21_root_ppc64le_debian12
//java:java17_nonroot_ppc64le_debian12
//java:java21_root_arm64_debian12
//java:java21_nonroot_amd64_debian13
//java:java17_debug_nonroot_arm64_debian12
//java:java21_root_amd64_debian13
//java:java17_debug_root_s390x_debian12
//java:java_base_root_ppc64le_debian12
//java:java_base_nonroot_s390x_debian12
//java:java21_debug_root_s390x_debian12
//java:java21_debug_root_ppc64le_debian12
//java:java21_debug_root_arm64_debian13
//java:java21_root_ppc64le_debian13
//java:java21_root_s390x_debian13
//java:java21_debug_root_arm64_debian12
//java:java17_debug_nonroot_s390x_debian12
//java:java21_debug_nonroot_s390x_debian12
//java:java21_root_s390x_debian12
//java:java_base_root_arm64_debian12
//java:java17_root_amd64_debian12
//java:java21_root_amd64_debian12
//java:java21_debug_nonroot_arm64_debian13
//java:java21_debug_root_amd64_debian12
//java:java17_debug_nonroot_ppc64le_debian12
//java:java17_root_s390x_debian12
//java:java21_debug_nonroot_arm64_debian12
//java:java21_nonroot_ppc64le_debian13
//java:java21_debug_nonroot_amd64_debian13
//java:java21_debug_root_amd64_debian13
//java:java25_root_s390x_debian13
//java:java_base_debug_nonroot_ppc64le_debian12
//java:java21_debug_nonroot_ppc64le_debian13
//java:java17_debug_root_arm64_debian12
//java:java25_nonroot_s390x_debian13
//java:java25_root_arm64_debian13
//java:java25_root_amd64_debian13
//java:java_base_debug_root_ppc64le_debian12
//java:java25_debug_root_arm64_debian13
//java:java17_debug_nonroot_amd64_debian12
//java:java25_root_ppc64le_debian13
//java:java25_nonroot_amd64_debian13
//java:java21_nonroot_s390x_debian13
//java:java21_debug_nonroot_amd64_debian12
//java:java21_nonroot_s390x_debian12
//java:java21_root_arm64_debian13
//java:java21_debug_nonroot_s390x_debian13
//java:java25_nonroot_ppc64le_debian13
//java:java25_debug_nonroot_amd64_debian13
//java:java25_debug_root_amd64_debian13
//java:java25_debug_nonroot_arm64_debian13
//java:java17_nonroot_amd64_debian12
//java:java25_debug_root_ppc64le_debian13
//java:java25_nonroot_arm64_debian13
//java:java25_debug_nonroot_ppc64le_debian13
//java:java17_nonroot_s390x_debian12
//java:java21_debug_nonroot_ppc64le_debian12
//java:java25_debug_root_s390x_debian13
//java:java21_debug_root_s390x_debian13
//java:java25_debug_nonroot_s390x_debian13
//java:java21_nonroot_ppc64le_debian12
//java:java21_nonroot_arm64_debian12
//java:java21_nonroot_arm64_debian13
//java:java21_debug_root_ppc64le_debian13
//java:java17_debug_nonroot_amd64_debian12
//java:java21_nonroot_amd64_debian12
//java:java17_root_arm64_debian12

You can check the details in the report here