E53E chore: 📢 Bump version to 1.22.0 by podman-desktop-bot · Pull Request #13634 · podman-desktop/podman-desktop · GitHub
[go: up one dir, main page]
Skip to content

chore: 📢 Bump version to 1.22.0 #13634

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Aug 19, 2025
Merged

chore: 📢 Bump version to 1.22.0 #13634

merged 1 commit into from
Aug 19, 2025

Conversation

podman-desktop-bot
Copy link
Contributor

📢 Bump version to 1.22.0

1.21.0 has been released.

Time to switch to the new 1.22.0 version 🥳

@benoitf
chore: bump version to 1.22.0
27528ee 
Signed-off-by: feloy <fbenoit@redhat.com>
@podman-desktop-bot podman-desktop-bot requested review from benoitf and a team as code owners August 19, 2025 06:44
@podman-desktop-bot podman-desktop-bot requested review from feloy and gastoner and removed request for a team August 19, 2025 06:44
@podman-desktop-bot podman-desktop-bot enabled auto-merge (rebase) August 19, 2025 06:44
@coderabbitai coderabbitai
Copy link
Contributor
coderabbitai bot commented Aug 19, 2025 •
edited
Loading
📝 Walkthrough

Walkthrough

Adds a new 1.21.0 release entry (dated 2025-08-19) to .flatpak-appdata.xml. Updates .github/ISSUE_TEMPLATE/bug_report.yml version dropdown: replaces 1.20.0 with 1.21.0 in place and inserts 1.20.0 after “next (development version)”. Bumps "version" fields from 1.21.0-next to 1.22.0-next in package.json and these extensions: compose, docker, kind, kube-context, kubectl-cli, lima, podman (packages/extension), registries. No other files or fields were changed.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • benoitf
  • dgolovin
  • SoniaSandler

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch bump-to-1.22.0

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
🪧 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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[bot]
coderabbitai bot reviewed Aug 19, 2025
View reviewed changes
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)
.github/ISSUE_TEMPLATE/bug_report.yml (1)

53-56: Reorder version dropdown to descending order

The dropdown in .github/ISSUE_TEMPLATE/bug_report.yml is currently listing versions as:

1.19.2
1.21.0
next (development version)
1.20.0
…

This puts an older patch before the latest stable release. Update lines 53–56 to:

--- a/.github/ISSUE_TEMPLATE/bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -53,7 +53,7
-        - "1.19.2"
-        - "1.21.0"
-        - "next (development version)"
-        - "1.20.0"
+        - "1.21.0"
+        - "next (development version)"
+        - "1.20.0"
+        - "1.19.2"

Optional quick check:

awk '/id:[[:space:]]*version/,/validations:/' .github/ISSUE_TEMPLATE/bug_report.yml \
  | sed -n 's/^\s*-\s*"\(.*\)"/\1/p' | head -n4

should output:

1.21.0
next (development version)
1.20.0
1.19.2
📜 Review details

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

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 59c0d00 and 27528ee.

📒 Files selected for processing (11)
  • .flatpak-appdata.xml (1 hunks)
  • .github/ISSUE_TEMPLATE/bug_report.yml (1 hunks)
  • extensions/compose/package.json (1 hunks)
  • extensions/docker/package.json (1 hunks)
  • extensions/kind/package.json (1 hunks)
  • extensions/kube-context/package.json (1 hunks)
  • extensions/kubectl-cli/package.json (1 hunks)
  • extensions/lima/package.json (1 hunks)
  • extensions/podman/packages/extension/package.json (1 hunks)
  • extensions/registries/package.json (1 hunks)
  • package.json (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (12)
  • GitHub Check: build website
  • GitHub Check: unit tests / macos-15
  • GitHub Check: unit tests / windows-2025
  • GitHub Check: unit tests / ubuntu-24.04
  • GitHub Check: smoke e2e tests (development)
  • GitHub Check: linter, formatters
  • GitHub Check: typecheck
  • GitHub Check: smoke e2e tests (production)
  • GitHub Check: macOS
  • GitHub Check: Windows
  • GitHub Check: Linux
  • GitHub Check: take screenshots
🔇 Additional comments (10)
extensions/podman/packages/extension/package.json (1)

5-5: LGTM on version bump.

Version updated to 1.22.0-next; no other manifest fields changed. Matches the PR intent.

extensions/kube-context/package.json (1)

5-5: LGTM on version bump.

Version moved to 1.22.0-next; consistent with the coordinated repo-wide update.

extensions/kind/package.json (1)

5-5: LGTM on version bump.

Manifest version set to 1.22.0-next; no functional changes introduced.

package.json (1)

6-6: Root version bump to 1.22.0-next verified

  • No lingering "1.21.0-next" entries across all package.json files.
  • All workspace packages meant to track the root release are now at 1.22.0-next.
  • Other packages retain independent versioning (e.g. 0.0.x, 1.9.0-next) as expected.
  • No .github/bug_report.yml or .flatpak-appdata.xml present in the repo.

Everything looks consistent—approving the version bump.

extensions/docker/package.json (1)

5-5: LGTM on version bump.

Aligned to 1.22.0-next; no other changes.

.flatpak-appdata.xml (1)

113-113: All checks passed for AppStream v1.21.0 release
Verified that:

  • The first <release> entry is version 1.21.0 dated 2025-08-19.
  • All listed package.json files (core and extensions) are bumped to 1.22.0-next.
  • The bug report template includes “1.21.0” and the “next (development version)” entry.

LGTM.

extensions/kubectl-cli/package.json (1)

5-5: Version bumped to 1.22.0-next — LGTM.

extensions/compose/package.json (1)

5-5: Version bumped to 1.22.0-next — LGTM.

extensions/lima/package.json (1)

5-5: Version bumped to 1.22.0-next — LGTM.

extensions/registries/package.json (1)

5-5: Version bumped to 1.22.0-next — LGTM.

@podman-desktop-bot podman-desktop-bot merged commit bd64020 into main Aug 19, 2025
24 checks passed
@podman-desktop-bot podman-desktop-bot deleted the bump-to-1.22.0 branch August 19, 2025 07:22
@podman-desktop-bot podman-desktop-bot added this to the 1.22.0 milestone Aug 19, 2025
This was referenced Sep 29, 2025
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@coderabbitai coderabbitai[bot] coderabbitai[bot] left review comments

@feloy feloy feloy approved these changes

@benoitf benoitf Awaiting requested review from benoitf benoitf is a code owner

@gastoner gastoner Awaiting requested review from gastoner gastoner is a code owner automatically assigned from podman-desktop/reviewers

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
1.22.0
Development

Successfully merging this pull request may close these issues.
2 participants
@podman-desktop-bot @feloy
0