8000 chore: update podman to v5.5.2 by benoitf · Pull Request #12960 · podman-desktop/podman-desktop · GitHub
[go: up one dir, main page]

Skip to content

Conversation

benoitf
Copy link
Collaborator
@benoitf benoitf commented Jun 25, 2025

What does this PR do?

update podman to v5.5.2
https://github.com/containers/podman/releases/tag/v5.5.2

Screenshot / video of UI

What issues does this PR fix or reference?

fixes #12959

How to test this PR?

  • Tests are covering the bug fix or the new feature

fixes #12959
Signed-off-by: Florent Benoit <fbenoit@redhat.com>
@benoitf benoitf requested a review from a team as a code owner June 25, 2025 06:49
@benoitf benoitf requested review from dgolovin, MarsKubeX and axel7083 and removed request for a team June 25, 2025 06:49
Copy link
Contributor
@sourcery-ai sourcery-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.

Hey @benoitf - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copy link
Contributor
coderabbitai bot commented Jun 25, 2025
📝 Walkthrough

Walkthrough

The changes update the Podman extension version from 5.5.1 to 5.5.2 in the JSON configuration file located at extensions/podman/packages/extension/src/podman5.json. All version references, including the release notes URL and installer filenames for Windows and macOS (x64, arm64, universal), have been modified to reflect the new 5.5.2 version. No changes to code logic or exported entities were made.

Assessment against linked issues

Objective Addressed Explanation
Update Podman extension to version 5.5.2 (#12959)

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes were found.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor
@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
extensions/podman/packages/extension/src/podman5.json (1)

2-22: Mind the mixed use of the v prefix in version strings.

The top-level "version" is "5.5.2" (no v), while every platform-specific "version" keeps the v prefix ("v5.5.2").
If downstream tooling parses these fields programmatically it may need extra handling for the mismatch.

Consider normalising the prefix across all version fields (either add v to the top level or drop it from the nested ones) unless consumers explicitly rely on the current convention.
No functional issue, just a consistency concern.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 46fc629 and 75c4adf.

📒 Files selected for processing (1)
  • extensions/podman/packages/extension/src/podman5.json (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (11)
  • GitHub Check: typecheck
  • GitHub Check: build website
  • GitHub Check: linter, formatters
  • GitHub Check: macOS
  • GitHub Check: smoke e2e tests (production)
  • GitHub Check: unit tests / ubuntu-24.04
  • GitHub Check: smoke e2e tests (development)
  • GitHub Check: unit tests / macos-15
  • GitHub Check: unit tests / windows-2022
  • GitHub Check: Windows
  • GitHub Check: Linux

Copy link
codecov bot commented Jun 25, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

@benoitf benoitf merged commit 97afbfa into podman-desktop:main Jun 26, 2025
21 checks passed
@podman-desktop-bot podman-desktop-bot added this to the 1.20.0 milestone Jun 26, 2025
@coderabbitai coderabbitai bot mentioned this pull request Aug 18, 2025
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update podman to v5.5.2
3 participants
0