lizhimins opened a new pull request, #7368:
URL: https://github.com/apache/rocketmq-dashboard/pull/7368
### What this changes
The demo RocketMQ cluster under `deploy/rocketmq/` was built from the
`develop` branch and tagged
`apache-rocketmq:develop`. A release should not ship pointing at an
unreleased moving target, and
`server/pom.xml` already declares the dependency baseline as
`rocketmq.version` 5.5.0.
- `Dockerfile`: default `ROCKETMQ_BRANCH` to the released tag
`rocketmq-all-5.5.0`
- `docker-compose.yml`: expose `ROCKETMQ_BRANCH` as a build arg so an
override needs no file edit,
and rename the image tag to `apache-rocketmq:5.5.0` on all six services
- `build.sh` / `README.md`: document the pinned version and the two places
to bump together
- `.claude/skills/*`: follow the new image tag so the deploy and DLQ
regression tooling keep
resolving the image they expect
Following `develop` stays possible for local debugging only:
`ROCKETMQ_BRANCH=develop ./build.sh`.
### Verification
- `docker compose config` renders `apache-rocketmq:5.5.0` for all six
services and
`ROCKETMQ_BRANCH: rocketmq-all-5.5.0` for the nameserver build.
- `rocketmq-all-5.5.0` exists on apache/rocketmq, and its `release-all`
profile keeps
`<finalName>rocketmq-${project.version}</finalName>` with the
`release.xml` descriptor (`dir`
format). The build output therefore stays
`distribution/target/rocketmq-5.5.0/rocketmq-5.5.0/{bin,conf,lib}` —
exactly what the Dockerfile's
`cp -r distribution/target/rocketmq-*/rocketmq-*/*` glob expects. Current
`develop` uses the same
`finalName` pattern, so the pinned build is layout-identical to what this
compose file builds today.
Part of the 3.0.0 release readiness follow-ups.
--
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]
