Repository navigation
CI: release and Neko version in VERSION, one build for all tags - #3
Merged
Merged
Conversation
f3l1x
force-pushed
the
release-version
branch
from
November 9, 2026 08:25
3676708 to
2878893
Compare
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
force-pushed
the
release-version
branch
from
November 9, 2026 10:27
2878893 to
adf7404
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Date versioning and a real CI build/push, like dockette/dummy and dockette/java.
VERSIONholdsVERSION=2026.11.09andNEKO_REF, the full commit ofholyfork/m1k1o-neko(7704fcc41399506fe91274b14e6473e100a949e9, "Chromium: pack chrome-mcp and playwright-mcp servers").make downloadfetches exactly that commit (shallow, HTTPS, nogit pull, no SSH).make build-chromiumruns the fork's./build -y(base image, then chromium app, linux/amd64). The upstream script passes the freshly builtneko/base:latestasBASE_IMAGE, so the chromium image does not use a pulled ghcrlatest.make test-dockeris a smoke test:chromiumexists in the image and the web UI answers on 8080 (--shm-size=2gb --cap-add SYS_ADMIN;NEKO_CHROME_FLAGSmust be set, the compose file sets it).test,lint(docs checks),build(download, build, smoke test; login and push on master only),release(GitHub release namedVERSION),docs(Docker Hub description). PRs build but never push. Triggers: push to master, pull_request, workflow_dispatch.make version,make releaseadded.Tags
dockette/neko:chromiumanddockette/neko:chromium-2026.11.09. Nolatest, no sha tags.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)
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).