7 Commits

Include renames

Author	SHA1	Message	Date
Kevin Veen-BirkenbachandClaude Opus 5.5	c2f0a56699	feat(publish): rebuild releases nightly and let stable follow the tested one ... Every image build now carries <version> and the immutable <version>.<unix-ts>; latest goes to the newest release on main, each prefix (2, 2.3) to the newest release starting with it, and stable to the release the git tag stable marks, which "Mark stable commit" sets only after all tests passed. publish-containers.yml runs daily at 03:00 UTC and on workflow_dispatch. A rebuild publishes the newest release and, when the git tag stable sits on an older one, that release too, so both get base-image security updates. compute-publish-container-info.sh emits the release list with each release's moving tags; image.sh takes them as --aliases instead of --stable. A platform build whose installed package set equals the published <version> pushes nothing, and a merge whose image index equals the published one only moves the tags not yet on it, without a new stamp. Only vX.Y.Z tags count as releases; v2.4.0-rc1 no longer moves 2 or 2.4. The build scripts come from the release commit: releases tagged before this change keep the old scripts until a newer release replaces them. tests/integration: 22 tests for release choice, aliases, the stable rebuild, the push skip and the triggers. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-04 18:38:42 +01:00
Kevin Veen-BirkenbachandClaude Opus 5.5	944b4cb663	ci(publish): build container images on native arch runners ... Each distro now builds amd64 on ubuntu-latest and arm64 on ubuntu-24.04-arm instead of emulating arm64 under QEMU. image.sh gains --platform, which pushes one <version>-<arch> tag, and --merge, which joins those tags under the release, stable and alias tags with buildx imagetools. The workflow splits into prepare, build and merge jobs; scripts/build/publish.sh follows the same sequence locally. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-11-01 00:53:16 +01:00
Kevin Veen-BirkenbachandClaude Opus 5	1e7642d358	chore: drop what the base-images refactor left behind ... scripts/docker/slim.sh survived the removal of the stage that copied and ran it, and nothing else referenced it. The README still offered a `Virgin` image type with `pkgmgr-arch-virgin` as its example, which is no longer published. Its second row was wrong independently of that refactor: the image does not contain Nix, it runs `make install`, which is scripts/installation/init.sh, and neither that nor entry.sh installs it. The section now states the tags compute_publish_tags() actually pushes, including the unsuffixed alias the default distribution gets, and points at base-images for the clean environment the virgin image used to serve. A missing blank line before a horizontal rule had also been rendering the paragraph above it as a heading. Three comment blocks explained what the repository used to do rather than what it does, in the Dockerfile, in scripts/build/publish.sh and in the Makefile. That belongs in the history, which is where it already is. Verified: markdownlint-cli2 on the README goes from 21 findings to 10, all remaining ones pre-existing and outside this section; `bash -n` on publish.sh and `make -n build` pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-18 16:22:45 +02:00
Kevin Veen-BirkenbachandClaude Opus 5	e45b6ed4a5	refactor(docker): consume the base images instead of building them ... The `virgin` stage installed the distribution build dependencies, and that layer now lives in its own repository: https://github.com/kevinveenbirkenbach/base-images. What remains here is one image per distribution that installs pkgmgr on top of it. `slim` goes with it: it was published for every distribution and pulled by nothing. scripts/build/base.sh stops pinning five upstream images and resolves ghcr.io/<owner>/base-<distro>:<tag> instead. Its env names follow the images repository rather than this one, so the code shows whose namespace that is. image.sh loses the --target axis, the -virgin/-slim tag suffixes with it, and passes --platform on push. Manjaro joins the set; os_resolver.sh already maps it onto arch, so it needs no dependency script of its own. The two virgin workflows pull the base image rather than building it. What they prove is unchanged: pkgmgr installs into an untouched container, as root and as an unprivileged user. test_distro_dependency_scripts_install_gpg_tools goes: it grepped the dependency scripts for gnupg, and those scripts are base-images' responsibility now, where the contract test runs `gpg --version` instead of reading a package list. Verified against locally built base images: the arch image builds FROM base-arch, and the full suite passes inside it - 405 unit, 90 integration and 49 e2e tests. Requires base-images to be published first; until then every build here fails at the pull. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-18 16:07:12 +02:00
Kevin Veen-Birkenbach	ac6981ad4d	feat(pkgmgr): add slim Docker image target and publish slim variants ... - add dedicated `slim` Dockerfile stage based on `full` - move image cleanup into slim stage via slim.sh - extend build script to support `--target slim` - publish pkgmgr-*-slim images for all distros https://chatgpt.com/share/69701a4e-b000-800f-be7e-162dcb93b1d2	2026-01-21 01:13:59 +01:00
Kevin Veen-Birkenbach	4e28eba883	refactor(ci,build,test): rename distro to PKGMGR_DISTRO for consistent environment handling ... https://chatgpt.com/share/693d6b63-12cc-800f-b55f-abc52ee7fb52	2025-12-13 14:34:15 +01:00
Kevin Veen-Birkenbach	2761e829cb	ci: add GHCR container publish pipeline with semantic tags ... Introduce a dedicated publish-containers workflow triggered after stable releases. Unify container build and publish logic via scripts, add buildx-based multi-tag publishing, default base image resolution, and Arch alias tags for latest/version/stable. https://chatgpt.com/share/693c836b-0b00-800f-9536-9e273abd0fb5	2025-12-12 22:04:39 +01:00