chore: bump default Camel JBang version to 4.20.0

[djelinek]

Summary by CodeRabbit

• Chores
  • Updated default Camel JBang version to 4.20.0.

[coderabbitai]

📝 Walkthrough

Walkthrough

Default Camel JBang version is updated from 4.19.0 to 4.20.0 in the extension configuration default and the release notes for version 2.11.0.

Changes

Camel JBang Version Upgrade

Layer / File(s)	Summary
Configuration Default package.json	Extension configuration default kaoto.camelJbang.version is bumped from 4.19.0 to 4.20.0.
Changelog Documentation CHANGELOG.md	Release 2.11.0 notes are updated to reflect the Camel JBang version upgrade target from 4.19.0 to 4.20.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• KaotoIO/vscode-kaoto#1333: Prior PR that performs the same version bump operation, incrementing Camel JBang from 4.18.0 to 4.19.0 in both configuration and changelog.

Suggested reviewers

• igarashitm

Poem

🐰 A version hops from old to new,
Four-twenty takes the kangaroo,
Config and changelog aligned with care,
JBang bounces through the air! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: bumping the default Camel JBang version from 4.19.0 to 4.20.0 in both package.json and CHANGELOG.md.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@CHANGELOG.md`:
- Line 3: The changelog line currently reads "Upgrade default Camel JBang
version from 4.18.0 to 4.20.0" which is incorrect for this PR; update that line
to "Upgrade default Camel JBang version from 4.19.0 to 4.20.0" so the release
note matches the actual previous default (edit the string in CHANGELOG.md that
contains "Upgrade default Camel JBang version from 4.18.0 to 4.20.0").

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 6c1b52e0-ac79-4084-8d6c-43577f2f1f76

📥 Commits

Reviewing files that changed from the base of the PR and between 434be25 and 4b46374.

📒 Files selected for processing (2)

• CHANGELOG.md
• package.json

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Release note baseline version looks incorrect.

This PR targets a bump from 4.19.0 to 4.20.0, but the changelog says 4.18.0 to 4.20.0. Please align this line with the actual previous default to avoid misleading release notes.

Suggested fix

-- Upgrade default Camel JBang version from 4.18.0 to 4.20.0
+- Upgrade default Camel JBang version from 4.19.0 to 4.20.0

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	- Upgrade default Camel JBang version from 4.18.0 to 4.20.0
	- Upgrade default Camel JBang version from 4.19.0 to 4.20.0

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CHANGELOG.md` at line 3, The changelog line currently reads "Upgrade default
Camel JBang version from 4.18.0 to 4.20.0" which is incorrect for this PR;
update that line to "Upgrade default Camel JBang version from 4.19.0 to 4.20.0"
so the release note matches the actual previous default (edit the string in
CHANGELOG.md that contains "Upgrade default Camel JBang version from 4.18.0 to
4.20.0").