Skip to content

Publish GHCR images and nightly production dependency releases - #16

Merged
Luen merged 3 commits into
mainfrom
codex/ghcr-nightly-production-releases
Nov 3, 2026
Merged

Luen merged 3 commits into
mainfrom
codex/ghcr-nightly-production-releases

Conversation

@Luen

@Luen Luen commented Nov 3, 2026

Copy link
Copy Markdown
Collaborator

The Odroid currently runs a locally built digest container, so Watchtower cannot pull new releases. Publish ghcr.io/rummerlab/media-alerts for ARM64 and AMD64, switch default Compose to the release image, and retain the container name, schedule, user IDs, environment, and ./data state mount. A local-build override remains available.

Add the crag-stats style nightly dependency update and conditional release flow at 00:37 Brisbane time. Pinned uv resolves universal hash-pinned production/development locks with a three-day release-age cutoff and bounded in-major upgrades. Only changes to the full production dependency graph trigger a patch tag, GitHub release, and latest image; developer-only and hash-only changes commit after tests without releasing. No changes is a no-op.

CI checks the real default container command as a non-root user with no network or credentials on native ARM64/AMD64. The reusable Docker release workflow validates the exact release commit and both architectures before publication. Nightly invokes it directly for GITHUB_TOKEN tags, refuses to rebase onto untested main changes, and atomically pushes the tested commit/tag. README covers migration, existing Watchtower, package access, and rollback.

Validation: offline suite and nine release-policy tests pass locally; the real updater is a no-op on the current locks; Ruff, actionlint, and production/local Compose validation pass. Actual image checks run in PR CI. The first image publication and nightly schedule require merging this PR. Branch rules must permit bot dependency commits to main.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Claude BugBot Analysis

I found no bugs I was confident enough to report in the dependency-release script, container smoke test, compose changes, or Dockerfile. I could not check .github/dependency-policy.json or the nightly workflows, because neither is in the diff. I did not read the lock files line by line.

No bugs were detected in this PR.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Claude BugBot Analysis

I found no bugs I'm confident about in the changed lines. I read the compose, Dockerfile, release script, smoke script and test changes, and checked the policy file, pyproject.toml and the smoke script's "Sleeping" log check against the repo. I did not read the lock-file hash lists (diff lines 453–559) or the workflow files.

No bugs were detected in this PR.

@Luen Luen left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Found [P2] in .github/workflows/docker-release.yml:98: rerunning an older stable tag unconditionally moves latest backward, causing Watchtower to downgrade deployments. Manual runs allow any existing stable tag, and queued tag pushes can run out of version order. Compare published stable release versions before advancing latest so older releases only publish their versioned image. I am fixing this with regression coverage. I also found README instructions copied from other apps (Scholar, a second service, and a podcast frontend) and will correct them for this repository. Existing bot reviews were read; they reported no findings.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Claude BugBot Analysis

No bugs found in the changes. I checked the Dockerfile, compose files, release script, smoke test and lock handling. None of them has a defect I could confirm. The smoke test's Playwright check is dead code, because the image defines no HEALTHCHECK, so it never runs.

No bugs were detected in this PR.

@Luen

Luen commented Nov 3, 2026

Copy link
Copy Markdown
Collaborator Author

Fixed the review finding in 95066b6. Release publication now compares all published stable versions before advancing latest, so rerunning an older release cannot downgrade Watchtower deployments. Added regression coverage for older retries, numeric version ordering, same-version retries, and first publication. Corrected the README and agent guidance to remove references to unrelated apps. Validation: 27 tests passed locally; Ruff lint/format and git diff --check passed; the new read-only release lookup was exercised against this repository. Updated PR CI is green, including native AMD64 and ARM64 build/smoke tests and security checks. Read the latest BugBot review: no additional confirmed defects. Its Playwright-branch observation is unreachable in this image and does not affect the scheduler smoke path. PR remains open.

@Luen Luen left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed current head 95066b6, including release/nightly workflows, native architecture build and smoke flow, dependency graph comparison and constraints, Compose migration, and all existing feedback. No additional confirmed actionable bugs found. The previously reported latest-tag downgrade issue and documentation corrections are already fixed in 95066b6; no further code changes were necessary in this pass.

Validation: 27 tests passed locally; Ruff lint/format checks and git diff --check passed. GitHub CI and BugBot completed successfully for this head; no inline review threads are outstanding. Live publication and nightly updates were not exercised during this review.

@Luen
Luen merged commit ed568d2 into main Nov 3, 2026
12 checks passed
@Luen
Luen deleted the codex/ghcr-nightly-production-releases branch November 3, 2026 04:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant