jzhao20230918 opened a new issue, #128:
URL: https://github.com/apache/rocketmq-docker/issues/128
### Problem
Apache RocketMQ 5.5.1 was released (GitHub release `rocketmq-all-5.5.1`,
vote result on dev@ 2026-08-26), but Docker Hub `apache/rocketmq` still only
has `5.5.0` / `latest` (pushed 2026-05-04). There is no `5.5.1` tag.
The image is supposed to be published automatically by
`.github/workflows/docker-publish.yml`, which runs hourly, looks up the latest
release via `getLatestRelease`, and builds/pushes if the tag is missing on
Docker Hub.
Looking at the Actions history of this repository:
- The last successful `docker-publish` run was on **2026-06-23**; runs in
July also succeeded.
- **Every run since August 2026 ends with `startup_failure`** (sampled 100
runs per month for August and September, all `startup_failure`; still failing
as of 2026-09-30).
Example: https://github.com/apache/rocketmq-docker/actions/runs/34047602884
`startup_failure` means the workflow does not even start, so this looks like
the same class of problem as #125 (fixed by #126, "update versions of docker
github actions") — most likely a referenced action version/SHA that is no
longer allowed or resolvable, or an org-level Actions policy change.
### Impact
5.5.1 contains the fix for apache/rocketmq#10284 (`JSONException: not
support unquoted name` in master→slave `SyncConsumerOffset`, fixed by
apache/rocketmq#10287). Users running the official 5.5.0 image in a
master/slave deployment keep hitting this error every minute and their slaves
hold incomplete consumer offsets, but they cannot upgrade using the official
image.
### Expected
- Fix the `docker-publish` workflow so it starts again.
- Publish `apache/rocketmq:5.5.1` (and update `latest`).
### Environment
- Docker Hub: `apache/rocketmq` tags checked on 2026-09-30 — latest is
`5.5.0`.
- GitHub release: `rocketmq-all-5.5.1` present.
Thanks!
--
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]
