christosgkoros commented on PR #25390:
URL: https://github.com/apache/camel/pull/25390#issuecomment-5258361934
Done in `4f5dcfd` — rebased onto `main` at 4.23.0-SNAPSHOT (45 commits,
clean, no conflicts) and re-stamped as 4.23.
Four files were hand edited; everything else is generated from them:
| File | Change |
|---|---|
| `components/camel-rest-postman/pom.xml` | `<firstVersion>` and the parent
`<version>` |
| `RestPostmanEndpoint.java` | `@UriEndpoint(firstVersion = "4.23.0", …)` |
| `rest-postman-component.adoc` | `:since: 4.23` |
| `bom/camel-bom/pom.xml` | this component's entry |
The BOM one is worth a note: that file uses literal versions rather than
`${project.version}`, and the repo-wide bump naturally could not touch a line
that did not exist on `main` yet, so my entry was the only `4.22.0-SNAPSHOT`
left sitting among `4.23.0-SNAPSHOT` neighbours.
Regenerated from those: both copies of `rest-postman.json`, the catalog copy
of the component page, `component.properties`, and the `Since:` javadoc in the
generated DSL builders. I checked the diffs on the shared builder files
(`ComponentsBuilderFactory`, `EndpointHeaderBuilders`,
`StaticEndpointBuilders`) line by line — each is a single `Since: 4.22` →
`4.23` next to a `camel-rest-postman` entry. The other `Since: 4.22` entries in
those files belong to components that did ship in 4.22 and are untouched.
Verified before pushing, the same chain CI runs:
```
mvn install -Dquickly # BUILD SUCCESS
mvn install -DskipTests -pl catalog/camel-catalog,core/camel-util,\
dsl/camel-componentdsl,dsl/camel-endpointdsl,dsl/camel-kamelet-main,docs
# BUILD SUCCESS
mvn install -Psourcecheck -pl components/camel-rest-postman # 170 tests,
SUCCESS
mvn test -pl components/camel-platform-http-vertx
-Dtest=PlatformHttpRestPostmanConsumerTest
# 8 tests, SUCCESS
git status --short # empty
```
Also confirmed no `4.22` reference remains anywhere this PR owns, and that
the upgrade guide still has zero diff against `main`.
Note this was a force-push, which has previously left the fork workflows in
`action_required` on this PR — they will likely need approving again before CI
reports.
_Claude Code on behalf of @christosgkoros_
--
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]
