build(flake): let mcphub keep its own nixpkgs #61
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/mcphub-own-nixpkgs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
This is the mcphub follow-up to #60. mcphub's module used to build its images with the host's packages, so #60's fix could not apply to it. Since marti/mcphub#54, the module deploys the flake's own images, which mcphub's CI builds. With the follows dropped, cum-tools asks for exactly those images and fetches them from cum-ci's cache.
Evidence
The images cum-tools deploys, compared with mcphub's
checks.x86_64-linux.*ata724e93:0yfqakyw…-mcphub.tar.gzqysdsk98…-mcphub.tar.gzqysdsk98…xqny9zds…-mcphub-runner.tar.gzf38qn1x2…-mcphub-runner.tar.gzf38qn1x2…nix flake check --no-build: all checks pass.trail check: no conflicts.Merge Danger
Door: two-way
Blast Radius: cum-tools
The mcphub, egress and runner containers restart onto newly tagged images. Their contents differ only in being built with mcphub's own nixpkgs. Migrations run first, as on every image change. If cum-ci's cache has already dropped the images, cum-tools builds them itself, as it does today.
🤖 Generated with Claude Code