| name | openreader-docker-release |
| description | Local Docker release workflow for OpenReader. Use before building or publishing GHCR images, tagging releases, validating image metadata, or reporting Docker release progress. |
OpenReader Docker Release
Use this skill before publishing Docker images.
Release policy
- Build locally. Do not use cloud Docker builds.
- Publish after a coherent validation slice passes backend, frontend, browser, and Docker gates appropriate to the change. A complete module boundary is preferred but not required when the user wants intermediate verification.
- Push Git commits to GitHub before or together with the Docker publish so the image can be traced to a remote commit.
- Preserve upgrade compatibility for mounted
data/, cache/, and library/.
Standard commands
Development image:
./scripts/docker-build-push.sh
Release image:
RELEASE=1 ./scripts/docker-build-push.sh
Inspect:
docker buildx imagetools inspect ghcr.io/changshengyu/openreader:latest
Required release report
Include:
- commit SHA and image tags;
- digest;
- completed items;
- allowed differences from upstream;
- unfinished items;
- validation summary;
- Docker/volume/backup compatibility result.