chore: 📢 Bump version to 1.21.0 #13080
Conversation
Signed-off-by: vzhukovs <fbenoit@redhat.com>
📝 WalkthroughWalkthroughThe changes include updating the version numbers from "1.20.0-next" to "1.21.0-next" in the root Suggested reviewers
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (2)
extensions/docker/package.json (1)
5-5: Same version-bump comment appliesCovered by the root-level verification script.
extensions/kind/package.json (1)
5-5: Same version-bump comment appliesCovered by the root-level verification script.
🧹 Nitpick comments (1)
.github/ISSUE_TEMPLATE/bug_report.yml (1)
54-57: Consider pre-adding “1.21.0” to the list
After this release goes GA, users on 1.21.0 will have to choose “next (development version)” until the template is updated again. Adding the soon-to-be current version now would save a follow-up PR.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 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)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: benoitf
PR: podman-desktop/podman-desktop#13043
File: packages/main/src/plugin/color-registry-inject.spec.ts:33-35
Timestamp: 2025-07-02T08:26:44.169Z
Learning: In test files for Podman Desktop, benoitf prefers partial mocking over complete mocking. Partial mocks that only implement the methods actually used in the test are sufficient and preferred over creating complete mock objects.
⏰ 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: unit tests / windows-2022
- GitHub Check: unit tests / ubuntu-24.04
- GitHub Check: unit tests / macos-15
- GitHub Check: smoke e2e tests (production)
- GitHub Check: smoke e2e tests (development)
- GitHub Check: typecheck
- GitHub Check: linter, formatters
- GitHub Check: Linux
- GitHub Check: macOS
- GitHub Check: Windows
- GitHub Check: build website
- GitHub Check: take screenshots
🔇 Additional comments (7)
.flatpak-appdata.xml (1)
112-114: Release entry correctly addedThe new 1.20.0 release is inserted in descending order, date format matches existing entries, and schema consistency is preserved.
extensions/registries/package.json (1)
5-5: Version bump detected – mirrors root package.jsonNo other changes; looks good.
extensions/kubectl-cli/package.json (1)
5-5: Version bump looks correct and consistent
No additional issues spotted; matches the overall 1.21.0-next bump across the repo.extensions/lima/package.json (1)
5-5: Version updated successfully
Change is purely semantic; nothing else to verify here.extensions/kube-context/package.json (1)
5-5: LGTM – aligned with global version
No functional impact.extensions/podman/packages/extension/package.json (1)
5-5: Podman extension version bump acknowledged
Everything else in the manifest remains untouched; good to go.extensions/compose/package.json (1)
5-5: Version bump looks good
"version": "1.21.0-next"correctly aligns this extension with the new release cycle.
| "repository": "https://github.com/podman-desktop/podman-desktop", | ||
| "homepage": "https://www.podman-desktop.io", | ||
| "version": "1.20.0-next", | ||
| "version": "1.21.0-next", |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Verify that every package.json now carries 1.21.0-next
The root version is bumped, but it’s easy to miss one of the many extension package.json files in the workspace.
Run the script below to confirm all packages are in lock-step:
🏁 Script executed:
#!/bin/bash
# Fails if any package.json (outside node_modules) has a version other than 1.21.0-next
set -e
expected="1.21.0-next"
fd package.json -E node_modules | while read -r file; do
v=$(jq -r '.version // empty' "$file")
[[ -n "$v" && "$v" != "$expected" ]] && { echo "Version mismatch in $file: $v"; exit 1; }
done
echo "✅ All package.json files are at $expected"Length of output: 1348
Version mismatch detected – sync all package.json versions
The version-check script reported a discrepancy:
• extensions/podman/packages/api/package.json: version is 0.0.1 (expected 1.21.0-next)
Please update that file’s "version" field to "1.21.0-next" so all packages remain in lock-step.
🤖 Prompt for AI Agents
In package.json at line 6, the version field is set to "1.21.0-next" but
extensions/podman/packages/api/package.json has a mismatched version "0.0.1".
Update the "version" field in extensions/podman/packages/api/package.json to
"1.21.0-next" to ensure all package versions are consistent.
📢 Bump version to 1.21.0
1.20.0 has been released.
Time to switch to the new 1.21.0 version 🥳