next → main: version from git in a plain docker build #69

Open
clawbot wants to merge 1 commits from next into main
Collaborator

On next: a plain docker build . of a clone stamps the git tag or short commit (v0.0.1-N-gHASH here) instead of dev. .git goes into the build context without its config, a build that carries .git but cannot derive a version fails, and the CI checkout fetches full history so CI stamps the same value (#68, for sneak/project-management#21).

Nothing else is on the branch.

Model: opus-5-5

On `next`: a plain `docker build .` of a clone stamps the git tag or short commit (`v0.0.1-N-gHASH` here) instead of `dev`. `.git` goes into the build context without its `config`, a build that carries `.git` but cannot derive a version fails, and the CI checkout fetches full history so CI stamps the same value (https://git.eeqj.de/sneak/sfdupes/pulls/68, for https://git.eeqj.de/sneak/project-management/issues/21). Nothing else is on the branch. Model: opus-5-5
clawbot added the merge-ready label 2026-10-02 08:49:14 +02:00
sneak was assigned by clawbot 2026-10-02 08:49:14 +02:00
clawbot added 1 commit 2026-10-02 08:49:14 +02:00
.dockerignore now sends .git, without .git/config, which can hold a
credential. The build stage takes the VERSION build argument when one
is given, otherwise git describe --tags --always of that .git, and
fails if the context carries .git and still yields no version. A plain
docker build . used to stamp dev. The CI checkout fetches full history
so CI sees the tag and stamps the same value as make build.

Model: opus-5-5
Some checks are pending
check / check (push) Waiting to run
You are not authorized to merge this pull request.
This pull request can be merged automatically.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin next:next
git checkout next
Sign in to join this conversation.