Skip to content

Conversation

@dolph
Copy link
Contributor

@dolph dolph commented Mar 13, 2025

SUMMARY

Debian 11 bullseye is now the oldstable release, and Debian 12 bookworm is the current stable release. The release of node does not have to change at the same time.

This is a follow up to #32240

TESTING INSTRUCTIONS

Build the base image and verify the upgrade.

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

Debian 11 bullseye is now the [oldstable release](https://www.debian.org/releases/), and Debian 12 bookworm is the current stable release. The release of node does not have to change at the same time.

This is a follow up to apache#32240
Copy link

@korbit-ai korbit-ai bot left a comment

Choose a reason for hiding this comment

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

I've completed my review and didn't find any issues.

Need a new review? Comment /korbit-review on this PR and I'll review your latest changes.

Korbit Guide: Usage and Customization

Interacting with Korbit

  • You can manually ask Korbit to review your PR using the /korbit-review command in a comment at the root of your PR.
  • You can ask Korbit to generate a new PR description using the /korbit-generate-pr-description command in any comment on your PR.
  • Too many Korbit comments? I can resolve all my comment threads if you use the /korbit-resolve command in any comment on your PR.
  • On any given comment that Korbit raises on your pull request, you can have a discussion with Korbit by replying to the comment.
  • Help train Korbit to improve your reviews by giving a 👍 or 👎 on the comments Korbit posts.

Customizing Korbit

  • Check out our docs on how you can make Korbit work best for you and your team.
  • Customize Korbit for your organization through the Korbit Console.

Current Korbit Configuration

General Settings
Setting Value
Review Schedule Automatic excluding drafts
Max Issue Count 10
Automatic PR Descriptions
Issue Categories
Category Enabled
Documentation
Logging
Error Handling
Readability
Design
Performance
Security
Functionality

Feedback and Support

Note

Korbit Pro is free for open source projects 🎉

Looking to add Korbit to your team? Get started with a free 2 week trial here

@dosubot dosubot bot added the infra:container Infra container and K8s label Mar 13, 2025
@michael-s-molina michael-s-molina added the review:checkpoint Last PR reviewed during the daily review standup label Mar 13, 2025
Copy link
Member

@mistercrunch mistercrunch left a comment

Choose a reason for hiding this comment

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

LGTM, say bye to your cached layers everyone!

@mistercrunch mistercrunch merged commit 2f6f5c6 into apache:master Mar 13, 2025
52 checks passed
@mistercrunch
Copy link
Member

Thanks for the PR! Keep 'em comin'!

@sadpandajoe sadpandajoe removed the review:checkpoint Last PR reviewed during the daily review standup label Mar 14, 2025
@michael-s-molina michael-s-molina added the v5.0 Label added by the release manager to track PRs to be included in the 5.0 branch label Mar 17, 2025
michael-s-molina pushed a commit that referenced this pull request Mar 20, 2025
@mistercrunch mistercrunch added 🍒 5.0.0 Cherry-picked to 5.0.0 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels labels Jul 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels infra:container Infra container and K8s size/XS v5.0 Label added by the release manager to track PRs to be included in the 5.0 branch 🍒 5.0.0 Cherry-picked to 5.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants