openreader-docker-release

Étoiles12

Forks3

Mis à jour6 juillet 2026 à 09:03

Local Docker release workflow for OpenReader. Use before building or publishing GHCR images, tagging releases, validating image metadata, or reporting Docker release progress.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

changshengyu

changshengyu/openreader

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

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.

Plus depuis ce dépôt

même dépôt

api-contract-compat

changshengyu/openreader

API compatibility workflow for OpenReader. Use when changing routes, Gin handlers, auth, request bodies, query parameters, response schemas, status codes, API errors, or frontend API clients.

2026-07-0612

booksource-parser-compat

changshengyu/openreader

Book source and parser compatibility workflow for OpenReader. Use when changing online sources, CSS selectors, XPath-like rules, RSS, chapter parsing, content cleaning, import preview/import, or local book parsing.

2026-07-0612

data-migration-compat

changshengyu/openreader

Data compatibility workflow for OpenReader. Use when changing GORM models, SQLite migrations, cache, library, uploads, local store, backup/restore, WebDAV storage, or persistent settings.

2026-07-0612

frontend-ux-compat

changshengyu/openreader

Frontend UX compatibility workflow for OpenReader. Use when changing Vue pages, routing, Pinia stores, reader UI, bookshelf, settings, import, WebDAV, sidebars, touch gestures, keyboard handling, or local persisted state.

2026-07-0612

openreader-backend

changshengyu/openreader

Backend architecture guardrails for OpenReader Go/Gin/GORM/SQLite changes. Use when modifying handlers, services, models, migrations, WebSocket sync, WebDAV, backup, imports, cache, or any backend API behavior.

2026-07-0612

openreader-frontend

changshengyu/openreader

Frontend guardrails for OpenReader Vue 3, Pinia, Element Plus, reader UI, Index workspace, mobile behavior, routing, and upstream visual/interaction alignment.

2026-07-0612

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.