The job runs inside a container, so -v "$PWD" mounted a path the Docker
daemon doesn't have and npm ci found no lockfile. Dockerfile.check sends
the repo as a build context instead. The gate itself worked: the image
build was skipped rather than pushing something unchecked.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A variable declared inside a try block but read after it shipped and broke
collection checks for a day; tests can't reach that path and node --check
only parses. ESLint flags it as no-undef. Wired into npm run lint / check
and into CI before the image build, so a failure stops the build.
Three findings fixed on the way: an unread argument, and two values
assigned then immediately replaced.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The auto GITHUB_TOKEN lacks package-write scope (push failed with
unauthorized: reqPackageAccess). Use a REGISTRY_TOKEN secret (Forgejo
token with write:package) and log in as the repo owner instead.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
On push to main (and v* tags), builds the Docker image and pushes it to
the Forgejo container registry at git.plexultra.com/dlawler489/printhive
(:latest and :<short-sha>). Uses the auto-provided Actions token with
packages:write; plain docker CLI so it only needs the checkout action.
Compose image reference updated to the Forgejo registry.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
