oscerd commented on PR #26783:
URL: https://github.com/apache/camel/pull/26783#issuecomment-5830077017
Post-merge housekeeping done: milestone 4.23.0, `bug` label, assigned,
CAMEL-24935 Resolved/Fixed.
**One thing I would like a committer to confirm before the bot ports this.**
The PR carries `port/camel-4.22.x` and `port/camel-4.18.x`, but this is a
deliberate behaviour break, not a pure bug fix: a route that reads the
`MessageId` from the body after `to("pulsar:...")` stops working and has to
read `CamelPulsarProducerMessageId` instead. On `main` that is fine — it is in
the 4.23 upgrade guide. On a patch release of an LTS line it means someone
upgrading 4.22.1 → 4.22.2 can have a working route stop working.
Two ways to square it:
1. **Drop the port labels** and let it ship in 4.23.0 only, which is the
usual home for a break of this kind. The bug it fixes —
`.to("pulsar:a").to("pulsar:b")` publishing a Java-serialized `MessageId` to
the second topic — has been there since 3.20, so it is not a regression that
needs urgent patching.
2. **Keep the ports** and add matching entries to
`camel-4x-upgrade-guide-4_22.adoc` and `camel-4x-upgrade-guide-4_18.adoc` on
`main`, per the convention that the per-line guides live there. I am happy to
open that doc PR.
I have left the labels as they are rather than deciding this myself. The
fixVersions on CAMEL-24935 currently say 4.18.5/4.22.2/4.23.0, which matches
option 2; if we take option 1 they should come back to 4.23.0 alone.
_Claude Code on behalf of oscerd_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
