Update fedora Docker tag to v43 - abandoned

[KubeArchitectBot]

This PR contains the following updates:

Package	Type	Update	Change
fedora	final	major	42 -> 43

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 821beb8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The Dockerfile located under gh-actions/ has been modified to update the base image. The previous image, fedora:42 with its specific SHA256 digest, has been replaced with fedora:43 and a new SHA256 digest. No other changes were made to the Dockerfile’s commands, labels, or settings.

Changes

File Path	Summary
gh-actions/Dockerfile	Updated base image from fedora:42 (sha256:70d5934128fe1b1abc97750dc358dad9cf499c11059f0ed720872fedcc4880d1) to fedora:43 (sha256:752797e54c0ea10dc7afa3e1d475e9bcab1bcef30e2b2eb4d27ab9f507ed02db)

Poem

I’m a rabbit hopping through the code,
Saw a Docker twist on my load.
Fedora 42 is now out the door,
Fedora 43 brings so much more!
With each change, I hop with glee, inciting a digital ode.
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0acac4e and 821beb8.

📒 Files selected for processing (1)

• gh-actions/Dockerfile (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• gh-actions/Dockerfile

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

gh-actions/Dockerfile (1)

2-32: Dockerfile Structure and Compatibility Check

The remainder of the Dockerfile remains unchanged and appears to follow standard practices for setting up a Fedora-based container. However, since the base image has changed to Fedora 43, please verify that:

• All package management steps (e.g., dnf -y upgrade --refresh and the installation of specific packages) are fully compatible with Fedora 43.
• No deprecations or changes in package naming affect your build process.

If any incompatibilities arise in future builds, consider updating the related instructions accordingly.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5db1ae5 and 6f5371f.

📒 Files selected for processing (1)

• gh-actions/Dockerfile (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build-fedora-image-workflow

🔇 Additional comments (1)

gh-actions/Dockerfile (1)

1-1: Base Image Update Verification

The base image has been updated from Fedora 42 to Fedora 43 with a new SHA256 digest. Please ensure that the digest
b00fc3cf4a22cd2d4b3bd645aa68097c3fc958b0f723fd7fe4fef26ee2dea3eb
matches the official Fedora 43 image published by the Fedora maintainers. This update meets the PR objectives, but a quick verification is recommended to avoid any unexpected issues due to digest mismatches.

[KubeArchitectBot]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[KubeArchitectBot]

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.