Bumping packages to latest stable versions#1831
Conversation
Signed-off-by: Distroless Bot <distroless-bot@google.com>
There was a problem hiding this comment.
Summary of Changes
Hello @distroless-bot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request focuses on updating various Debian package dependencies to their latest stable versions. The primary change involves updating the snapshot URLs in the lock files and YAML configurations to pull from a more recent Debian archive. Notably, the versions of libssl3 and openssl have been explicitly bumped to address potential security or stability improvements.
Highlights
- Snapshot URL Updates: Updated the snapshot URLs across multiple .lock.json and .yaml files from 20250613T202933Z to 20250731T202225Z. This ensures that the builds pull from a more recent Debian snapshot.
- libssl3 Version Bump: Bumped libssl3 from version 3.0.16-1
deb12u1 to 3.0.17-1deb12u1 for amd64, arm64, armhf, ppc64el, and s390x architectures. - openssl Version Bump: Bumped openssl from version 3.0.16-1
deb12u1 to 3.0.17-1deb12u1 for amd64, arm64, armhf, ppc64el, and s390x architectures. - Checksum Updates: Updated checksums for libssl3 and openssl corresponding to their new versions.
- Other Package Snapshot URL Updates: Other packages like base-files, ca-certificates, libc6, libc-bin, tzdata, gcc-12-base, libgcc-s1, libgomp1, libstdc++6, fontconfig-config, fonts-dejavu-core, libbrotli1, libcrypt1, libexpat1, libfontconfig1, libfreetype6, libglib2.0-0, libgraphite2-3, libharfbuzz0b, libjpeg62-turbo, liblcms2-2, libpcre2-8-0, libpng16-16, libuuid1, openjdk-17-jdk-headless, openjdk-17-jre-headless, zlib1g, dash, libdb5.3, libffi8, libgssapi-krb5-2, libk5crypto3, libkeyutils1, libkrb5-3, libkrb5support0, liblzma5, libncursesw6, libnsl2, libpython3.11-minimal, libpython3.11-stdlib, libreadline8, libsqlite3-0, libtinfo6, libtirpc3, python3-distutils, and python3.11-minimal had their snapshot URLs updated, but their versions remained consistent.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| 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 issue 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 or fill out our survey to provide feedback.
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
-
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. ↩
There was a problem hiding this comment.
Code Review
This pull request updates various packages to their latest stable versions, most notably OpenSSL to 3.0.17-1~deb12u1 which includes security fixes. The changes also involve updating Debian snapshot URLs across several configuration and lock files. The updates are consistent and correctly applied. My review includes suggestions to improve the maintainability of the YAML configuration files by using anchors to avoid redundant URL definitions.
| sources: | ||
| - channel: bookworm main | ||
| url: https://snapshot.debian.org/archive/debian/20250613T202933Z | ||
| url: https://snapshot.debian.org/archive/debian/20250731T202225Z | ||
| - channel: bookworm-updates main | ||
| url: https://snapshot.debian.org/archive/debian/20250613T202933Z | ||
| url: https://snapshot.debian.org/archive/debian/20250731T202225Z | ||
| - channel: bookworm-security main | ||
| url: https://snapshot.debian.org/archive/debian-security/20250613T202933Z | ||
| url: https://snapshot.debian.org/archive/debian-security/20250731T202225Z |
There was a problem hiding this comment.
To improve maintainability, you could use a YAML anchor to avoid repeating the same URL for bookworm main and bookworm-updates main. This makes it easier to update in the future.
sources:
- channel: bookworm main
url: &debian_url https://snapshot.debian.org/archive/debian/20250731T202225Z
- channel: bookworm-updates main
url: *debian_url
- channel: bookworm-security main
url: https://snapshot.debian.org/archive/debian-security/20250731T202225Z
| sources: | ||
| - channel: bookworm main | ||
| url: https://snapshot.debian.org/archive/debian/20250613T202933Z | ||
| url: https://snapshot.debian.org/archive/debian/20250731T202225Z | ||
| - channel: bookworm-updates main | ||
| url: https://snapshot.debian.org/archive/debian/20250613T202933Z | ||
| url: https://snapshot.debian.org/archive/debian/20250731T202225Z | ||
| - channel: bookworm-security main | ||
| url: https://snapshot.debian.org/archive/debian-security/20250613T202933Z | ||
| url: https://snapshot.debian.org/archive/debian-security/20250731T202225Z |
There was a problem hiding this comment.
To improve maintainability, you could use a YAML anchor to avoid repeating the same URL for bookworm main and bookworm-updates main. This makes it easier to update in the future.
sources:
- channel: bookworm main
url: &debian_url https://snapshot.debian.org/archive/debian/20250731T202225Z
- channel: bookworm-updates main
url: *debian_url
- channel: bookworm-security main
url: https://snapshot.debian.org/archive/debian-security/20250731T202225Z
| sources: | ||
| - channel: bookworm main | ||
| url: https://snapshot.debian.org/archive/debian/20250613T202933Z | ||
| url: https://snapshot.debian.org/archive/debian/20250731T202225Z | ||
| - channel: bookworm-updates main | ||
| url: https://snapshot.debian.org/archive/debian/20250613T202933Z | ||
| url: https://snapshot.debian.org/archive/debian/20250731T202225Z | ||
| - channel: bookworm-security main | ||
| url: https://snapshot.debian.org/archive/debian-security/20250613T202933Z | ||
| url: https://snapshot.debian.org/archive/debian-security/20250731T202225Z |
There was a problem hiding this comment.
To improve maintainability, you could use a YAML anchor to avoid repeating the same URL for bookworm main and bookworm-updates main. This makes it easier to update in the future.
sources:
- channel: bookworm main
url: &debian_url https://snapshot.debian.org/archive/debian/20250731T202225Z
- channel: bookworm-updates main
url: *debian_url
- channel: bookworm-security main
url: https://snapshot.debian.org/archive/debian-security/20250731T202225Z
|
🌳 🔄 Image Check This pull request has modified the following images: //base:base_root_amd64_debian12
//base:debug_nonroot_amd64_debian12
//base:debug_root_amd64_debian12
//base:base_root_amd64_debian12
//base:base_nonroot_amd64_debian12
//base:debug_root_amd64_debian12
//base:debug_nonroot_amd64_debian12
//base:debug_nonroot_arm64_debian12
//base:base_nonroot_amd64_debian12
//base:base_root_arm_debian12
//base:base_nonroot_arm64_debian12
//base:debug_nonroot_arm64_debian12
//base:base_root_arm_debian12
//base:base_root_arm64_debian12
//base:base_nonroot_arm_debian12
//base:debug_root_arm_debian12
//base:base_root_s390x_debian12
//base:base_nonroot_ppc64le_debian12
//base:base_root_s390x_debian12
//base:debug_root_s390x_debian12
//base:debug_nonroot_arm_debian12
//base:debug_root_arm64_debian12
//base:base_root_ppc64le_debian12
//base:debug_root_arm_debian12
//base:base_root_ppc64le_debian12
//base:debug_nonroot_ppc64le_debian12
//base:debug_root_ppc64le_debian12
//base:debug_root_s390x_debian12
//base:base_root_arm64_debian12
//base:debug_nonroot_arm_debian12
//base:debug_nonroot_ppc64le_debian12
//base:debug_nonroot_s390x_debian12
//base:base_nonroot_arm64_debian12
//base:debug_nonroot_s390x_debian12
//base:base_nonroot_s390x_debian12
//cc:cc_nonroot_amd64_debian12
//cc:debug_nonroot_amd64_debian12
//cc:cc_root_arm64_debian12
//cc:debug_nonroot_amd64_debian12
//cc:debug_root_arm64_debian12
//cc:debug_nonroot_arm64_debian12
//cc:cc_root_arm64_debian12
//cc:debug_root_arm_debian12
//base:base_nonroot_s390x_debian12
//cc:debug_root_arm_debian12
//cc:cc_root_arm_debian12
//cc:cc_nonroot_arm_debian12
//cc:debug_nonroot_s390x_debian12
//cc:cc_nonroot_ppc64le_debian12
//cc:cc_root_arm_debian12
//cc:cc_nonroot_arm_debian12
//cc:debug_root_ppc64le_debian12
//cc:debug_root_s390x_debian12
//cc:cc_nonroot_arm64_debian12
//cc:cc_root_s390x_debian12
//cc:debug_nonroot_ppc64le_debian12
//cc:debug_root_arm64_debian12
//cc:cc_root_amd64_debian12
//cc:cc_nonroot_ppc64le_debian12
//cc:debug_root_ppc64le_debian12
//cc:debug_nonroot_arm_debian12
//python3:python3_root_amd64_debian12
//base:base_nonroot_ppc64le_debian12
//python3:debug_root_amd64_debian12
//base:debug_root_ppc64le_debian12
//python3:python3_root_amd64_debian12
//cc:cc_nonroot_arm64_debian12
//cc:cc_nonroot_amd64_debian12
//cc:cc_root_amd64_debian12
//python3:debug_nonroot_amd64_debian12
//python3:debug_nonroot_arm64_debian12
//python3:debug_root_arm64_debian12
//cc:cc_root_s390x_debian12
//cc:cc_root_ppc64le_debian12
//cc:cc_root_ppc64le_debian12
//cc:debug_nonroot_ppc64le_debian12
//cc:debug_root_amd64_debian12
//cc:cc_nonroot_s390x_debian12
//cc:debug_root_amd64_debian12
//cc:debug_nonroot_arm64_debian12
//base:base_nonroot_arm_debian12
//python3:python3_nonroot_amd64_debian12
//python3:python3_nonroot_amd64_debian12
//cc:debug_root_s390x_debian12
//python3:python3_root_arm64_debian12
//python3:python3_root_arm64_debian12
//nodejs:nodejs20_debug_nonroot_amd64_debian12
//python3:python3_nonroot_arm64_debian12
//python3:debug_nonroot_arm64_debian12
//python3:debug_root_amd64_debian12
//nodejs:nodejs20_root_amd64_debian12
//base:debug_root_arm64_debian12
//cc:cc_nonroot_s390x_debian12
//nodejs:nodejs20_debug_root_arm64_debian12
//python3:debug_nonroot_amd64_debian12
//cc:debug_nonroot_s390x_debian12
//python3:python3_nonroot_arm64_debian12
//python3:debug_root_arm64_debian12
//nodejs:nodejs20_nonroot_arm_debian12
//cc:debug_nonroot_arm_debian12
//nodejs:nodejs20_root_arm_debian12
//nodejs:nodejs20_debug_root_arm64_debian12
//nodejs:nodejs20_debug_root_amd64_debian12
//nodejs:nodejs20_root_arm64_debian12
//nodejs:nodejs20_debug_root_s390x_debian12
//nodejs:nodejs20_debug_root_amd64_debian12
//nodejs:nodejs20_debug_root_s390x_debian12
//nodejs:nodejs20_debug_nonroot_arm_debian12
//nodejs:nodejs20_nonroot_amd64_debian12
//nodejs:nodejs20_nonroot_amd64_debian12
//nodejs:nodejs20_nonroot_arm64_debian12
//nodejs:nodejs20_root_arm_debian12
//nodejs:nodejs20_debug_nonroot_s390x_debian12
//nodejs:nodejs20_debug_root_ppc64le_debian12
//nodejs:nodejs20_nonroot_s390x_debian12
//nodejs:nodejs20_nonroot_ppc64le_debian12
//nodejs:nodejs20_nonroot_ppc64le_debian12
//nodejs:nodejs20_nonroot_arm64_debian12
//nodejs:nodejs20_nonroot_arm_debian12
//nodejs:nodejs20_debug_nonroot_s390x_debian12
//nodejs:nodejs20_debug_root_arm_debian12
//nodejs:nodejs20_debug_nonroot_arm_debian12
//nodejs:nodejs20_root_arm64_debian12
//nodejs:nodejs20_debug_nonroot_ppc64le_debian12
//nodejs:nodejs20_root_amd64_debian12
//nodejs:nodejs22_debug_nonroot_amd64_debian12
//nodejs:nodejs20_nonroot_s390x_debian12
//nodejs:nodejs20_root_s390x_debian12
//nodejs:nodejs20_debug_nonroot_ppc64le_debian12
//nodejs:nodejs20_debug_nonroot_amd64_debian12
//nodejs:nodejs20_root_ppc64le_debian12
//nodejs:nodejs22_debug_root_arm_debian12
//nodejs:nodejs20_debug_root_arm_debian12
//nodejs:nodejs20_debug_nonroot_arm64_debian12
//nodejs:nodejs22_debug_root_amd64_debian12
//nodejs:nodejs22_root_arm64_debian12
//nodejs:nodejs22_nonroot_arm_debian12
//nodejs:nodejs22_nonroot_amd64_debian12
//nodejs:nodejs22_debug_root_arm_debian12
//nodejs:nodejs22_nonroot_amd64_debian12
//nodejs:nodejs22_debug_root_s390x_debian12
//nodejs:nodejs22_root_arm_debian12
//nodejs:nodejs20_debug_root_ppc64le_debian12
//nodejs:nodejs22_root_arm_debian12
//nodejs:nodejs22_nonroot_s390x_debian12
//nodejs:nodejs22_nonroot_arm64_debian12
//nodejs:nodejs22_root_s390x_debian12
//nodejs:nodejs22_debug_root_arm64_debian12
//nodejs:nodejs22_root_arm64_debian12
//nodejs:nodejs22_debug_root_arm64_debian12
//nodejs:nodejs22_debug_root_amd64_debian12
//nodejs:nodejs24_root_amd64_debian12
//nodejs:nodejs22_debug_nonroot_ppc64le_debian12
//nodejs:nodejs22_nonroot_arm64_debian12
//nodejs:nodejs22_nonroot_s390x_debian12
//nodejs:nodejs22_root_ppc64le_debian12
//nodejs:nodejs22_nonroot_ppc64le_debian12
//nodejs:nodejs22_debug_nonroot_arm_debian12
//nodejs:nodejs22_debug_nonroot_ppc64le_debian12
//nodejs:nodejs22_debug_nonroot_arm_debian12
//nodejs:nodejs22_debug_root_s390x_debian12
//nodejs:nodejs22_debug_root_ppc64le_debian12
//nodejs:nodejs24_root_amd64_debian12
//nodejs:nodejs20_root_s390x_debian12
//nodejs:nodejs20_root_ppc64le_debian12
//nodejs:nodejs22_debug_nonroot_arm64_debian12
//nodejs:nodejs22_root_ppc64le_debian12
//nodejs:nodejs24_debug_nonroot_amd64_debian12
//nodejs:nodejs22_debug_nonroot_s390x_debian12
//nodejs:nodejs24_root_s390x_debian12
//nodejs:nodejs24_debug_nonroot_arm64_debian12
//nodejs:nodejs22_nonroot_ppc64le_debian12
//nodejs:nodejs24_debug_root_amd64_debian12
//nodejs:nodejs24_debug_root_arm64_debian12
//nodejs:nodejs24_nonroot_s390x_debian12
//nodejs:nodejs24_debug_root_arm64_debian12
//nodejs:nodejs24_root_ppc64le_debian12
//nodejs:nodejs22_root_s390x_debian12
//nodejs:nodejs24_debug_root_s390x_debian12
//nodejs:nodejs24_nonroot_arm64_debian12
//nodejs:nodejs24_debug_nonroot_s390x_debian12
//nodejs:nodejs24_debug_nonroot_amd64_debian12
//nodejs:nodejs24_nonroot_ppc64le_debian12
//nodejs:nodejs24_root_ppc64le_debian12
//nodejs:nodejs22_nonroot_arm_debian12
//nodejs:nodejs24_nonroot_amd64_debian12
//nodejs:nodejs24_debug_nonroot_ppc64le_debian12
//nodejs:nodejs24_nonroot_amd64_debian12
//nodejs:nodejs24_nonroot_arm64_debian12
//nodejs:nodejs22_debug_nonroot_amd64_debian12
//nodejs:nodejs24_debug_nonroot_arm64_debian12
//nodejs:nodejs24_root_arm64_debian12
//nodejs:nodejs24_root_s390x_debian12
//nodejs:nodejs22_debug_nonroot_s390x_debian12
//nodejs:nodejs24_debug_nonroot_s390x_debian12
//nodejs:nodejs24_nonroot_ppc64le_debian12
//nodejs:nodejs20_debug_nonroot_arm64_debian12
//nodejs:nodejs24_nonroot_s390x_debian12
//nodejs:nodejs24_debug_root_ppc64le_debian12
//nodejs:nodejs24_debug_root_s390x_debian12
//nodejs:nodejs24_debug_nonroot_ppc64le_debian12
//nodejs:nodejs22_root_amd64_debian12
//nodejs:nodejs24_debug_root_amd64_debian12
//nodejs:nodejs22_debug_root_ppc64le_debian12
//nodejs:nodejs24_root_arm64_debian12
//nodejs:nodejs24_debug_root_ppc64le_debian12
//nodejs:nodejs22_root_amd64_debian12
//nodejs:nodejs22_debug_nonroot_arm64_debian12You can check the details in the report here |
Bumping packages to latest stable version