Skip to content

Bump version to 4.24.0-SNAPSHOT - #27901

Merged
gzurowski merged 2 commits into
mainfrom
bump-4.24
Oct 15, 2026
Merged

gzurowski merged 2 commits into
mainfrom
bump-4.24

Conversation

@gzurowski

Copy link
Copy Markdown
Member

Description

Since 4.23 is released, bump version to 4.24.0-SNAPSHOT on the main branch.

@gzurowski
gzurowski requested review from davsclaus and oscerd and removed request for davsclaus October 15, 2026 12:36
@github-actions

Copy link
Copy Markdown
Contributor

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

  • First-time contributors require MANUAL approval for the GitHub Actions to run
  • You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
  • You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
  • Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

@gzurowski
gzurowski merged commit 5686684 into main Oct 15, 2026
8 of 14 checks passed
@github-actions
github-actions Bot deleted the bump-4.24 branch October 15, 2026 12:45
@github-actions

Copy link
Copy Markdown
Contributor

⚠️ Generated files are out of date

The CI build regenerated files that are not committed on this PR.

If Allow edits from maintainers is enabled, a maintainer bot will automatically
push a "Regen" commit to this branch shortly.

Otherwise, you can apply the patch manually — the missing changes are available
as the regen-patch artifact of that run:

gh pr checkout 27901 --repo apache/camel
gh run download 38735915273 --repo apache/camel -n regen-patch
git apply --index regen.patch && rm regen.patch pr-number
git commit -m "Regen" && git push

Alternatively, run ./etc/scripts/regen.sh locally and commit the resulting changes.
If the patch does not apply cleanly, update the branch from the base branch first —
the patch was generated against the merge with the base branch.

@gnodet-bot gnodet-bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The mechanical version bump (4.23.0-SNAPSHOT → 4.24.0-SNAPSHOT) looks correct across all files. However, the find-and-replace only targeted -SNAPSHOT occurrences — four comment/documentation examples still pair 4.24.0-SNAPSHOT with 4.23.0 as the stripped result, which is now incorrect.

This review was generated by an AI agent, Hermès on behalf of @gnodet.

Comment thread AGENTS.md
- Read the `<version>` from the root `pom.xml` on the PR's **target branch** (e.g., `main`,
`camel-4.18.x`).
- Strip the `-SNAPSHOT` suffix to get the milestone name (e.g., `4.23.0-SNAPSHOT` → `4.23.0`).
- Strip the `-SNAPSHOT` suffix to get the milestone name (e.g., `4.24.0-SNAPSHOT` → `4.23.0`).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Stale example: The SNAPSHOT was bumped to 4.24.0-SNAPSHOT but the derived version in this example was left as 4.23.0. AI agents reading these guidelines after the merge will apply the wrong milestone.

Suggested change
- Strip the `-SNAPSHOT` suffix to get the milestone name (e.g., `4.24.0-SNAPSHOT` → `4.23.0`).
- Strip the `-SNAPSHOT` suffix to get the milestone name (e.g., `4.24.0-SNAPSHOT` → `4.24.0`).

- **Scope-too-large redirect:** create a Jira issue directly
- **Merge procedure:**
1. Derive milestone from target branch: read `<version>` from root `pom.xml` on the target branch and strip `-SNAPSHOT` (e.g., `4.23.0-SNAPSHOT` → `4.23.0`)
1. Derive milestone from target branch: read `<version>` from root `pom.xml` on the target branch and strip `-SNAPSHOT` (e.g., `4.24.0-SNAPSHOT` → `4.23.0`)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Stale example: Same issue — 4.24.0-SNAPSHOT paired with 4.23.0. Should be 4.24.0.

Suggested change
1. Derive milestone from target branch: read `<version>` from root `pom.xml` on the target branch and strip `-SNAPSHOT` (e.g., `4.24.0-SNAPSHOT` → `4.23.0`)
1. Derive milestone from target branch: read `<version>` from root `pom.xml` on the target branch and strip `-SNAPSHOT` (e.g., `4.24.0-SNAPSHOT` → `4.24.0`)

@@ -84,7 +84,7 @@ public CamelCatalog loadCatalog(String runtime, String camelVersion, String plat
boolean hasVersion = camelVersion != null && !camelVersion.isBlank() && !camelVersion.isEmpty()
&& Character.isDigit(camelVersion.trim().charAt(0));
if (hasVersion && sameAsDefault(camelVersion)) {
// the version in use (4.23.0 for a 4.23.0-SNAPSHOT build): nothing to download
// the version in use (4.23.0 for a 4.24.0-SNAPSHOT build): nothing to download

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

💡 Stale comment: The comment says 4.23.0 for a 4.24.0-SNAPSHOT build — the stripped version should now be 4.24.0.

Suggested change
// the version in use (4.23.0 for a 4.24.0-SNAPSHOT build): nothing to download
// the version in use (4.24.0 for a 4.24.0-SNAPSHOT build): nothing to download

@@ -59,7 +59,7 @@ void validatesValidMainProperty() {

@Test
void theRunningVersionWithoutSnapshotIsTheDefaultCatalog() {
// an assistant that reads "4.23.0-SNAPSHOT" from the server asks for 4.23.0, which is not on Maven Central
// an assistant that reads "4.24.0-SNAPSHOT" from the server asks for 4.23.0, which is not on Maven Central

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

💡 Stale comment: Says asks for 4.23.0 — after the bump, the stripped SNAPSHOT version is 4.24.0.

Suggested change
// an assistant that reads "4.24.0-SNAPSHOT" from the server asks for 4.23.0, which is not on Maven Central
// an assistant that reads "4.24.0-SNAPSHOT" from the server asks for 4.24.0, which is not on Maven Central

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants