Skip to content

CI: release and Neko version in VERSION, one build for all tags - #3

Merged
f3l1x merged 2 commits into
masterfrom
release-version
Nov 9, 2026
Merged

f3l1x merged 2 commits into
masterfrom
release-version

Conversation

@f3l1x

@f3l1x f3l1x commented Nov 9, 2026

Copy link
Copy Markdown
Member

What

Date versioning and a real CI build/push, like dockette/dummy and dockette/java.

  • VERSION holds VERSION=2026.11.09 and NEKO_REF, the full commit of holyfork/m1k1o-neko (7704fcc41399506fe91274b14e6473e100a949e9, "Chromium: pack chrome-mcp and playwright-mcp servers").
  • make download fetches exactly that commit (shallow, HTTPS, no git pull, no SSH).
  • make build-chromium runs the fork's ./build -y (base image, then chromium app, linux/amd64). The upstream script passes the freshly built neko/base:latest as BASE_IMAGE, so the chromium image does not use a pulled ghcr latest.
  • make test-docker is a smoke test: chromium exists in the image and the web UI answers on 8080 (--shm-size=2gb --cap-add SYS_ADMIN; NEKO_CHROME_FLAGS must be set, the compose file sets it).
  • Workflow: test, lint (docs checks), build (download, build, smoke test; login and push on master only), release (GitHub release named VERSION), docs (Docker Hub description). PRs build but never push. Triggers: push to master, pull_request, workflow_dispatch.
  • make version, make release added.

Tags

dockette/neko:chromium and dockette/neko:chromium-2026.11.09. No latest, no sha tags.

$ make -n push-chromium
docker push dockette/neko:chromium
docker push dockette/neko:chromium-2026.11.09

The fork has no tags; it is based on upstream n.eko master after v3.2.0 plus 9 fork commits (Debian 13 images). That is documented in the README only, not in the tags.

Local test (Apple Silicon, linux/amd64 emulated)

make test                       # docker compose config: valid
make download build-chromium DOCKER_CHROMIUM_IMAGE=neko-ver-test:chromium   # built OK
  docker tag neko/chromium neko-ver-test:chromium
  docker tag neko/chromium neko-ver-test:chromium-2026.11.09
make test-docker DOCKER_CHROMIUM_IMAGE=neko-ver-test:chromium
  /usr/bin/chromium
  (port 8080 answered, exit 0)

Note: the workflow only runs on push to master and on PRs, so the push/release/docs jobs are only exercised after merge (they need DOCKERHUB_USERNAME/DOCKERHUB_TOKEN).

f3l1x added 2 commits November 9, 2026 11:26
VERSION holds the release date and the pinned commit of holyfork/m1k1o-neko. CI clones that commit, builds the image, smoke tests it and on master pushes chromium and chromium-VERSION, then creates a GitHub release and syncs the Docker Hub description.
@f3l1x
f3l1x merged commit 2a85574 into master Nov 9, 2026
4 checks passed
@f3l1x
f3l1x deleted the release-version branch November 9, 2026 13:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant