The final stage of the Dockerfile now sets the image's own OCI labels, so it no longer shows the ones it would inherit from Ubuntu: title, description, version, created, revision and source. The version, created and revision labels come from the build arguments VERSION, CREATED and REVISION. Each defaults to unknown, so a plain docker build . still replaces Ubuntu's values. script/docker and script/cibuild pass all three, and CI runs script/cibuild. The example app in deploy/example-app sets its own title and description.
What the diff does not show:
The final stage's ARG VERSION=unknown belongs to that stage only. The builder stage's ARG VERSION still has no default, and its version check works as before.
The example app takes version, created, revision and source from the smallwebwaf image it is built on, which is built from the same checkout.
Disclosures:
Not built or tested locally, by sneak's order on the issue: CI tests it.
Labelled merge-ready and assigned to sneak with no review, by his order on the issue. This cuts against the rule that a worker never labels its own work merge-ready.
Model: opus-5-5
Closes https://git.eeqj.de/sneak/smallwebwaf/issues/216.
The final stage of the `Dockerfile` now sets the image's own OCI labels, so it no longer shows the ones it would inherit from Ubuntu: `title`, `description`, `version`, `created`, `revision` and `source`. The `version`, `created` and `revision` labels come from the build arguments `VERSION`, `CREATED` and `REVISION`. Each defaults to `unknown`, so a plain `docker build .` still replaces Ubuntu's values. `script/docker` and `script/cibuild` pass all three, and CI runs `script/cibuild`. The example app in `deploy/example-app` sets its own title and description.
What the diff does not show:
- The final stage's `ARG VERSION=unknown` belongs to that stage only. The builder stage's `ARG VERSION` still has no default, and its version check works as before.
- The example app takes `version`, `created`, `revision` and `source` from the smallwebwaf image it is built on, which is built from the same checkout.
Disclosures:
- Not built or tested locally, by sneak's order on the issue: CI tests it.
- Labelled `merge-ready` and assigned to sneak with no review, by his order on the issue. This cuts against the rule that a worker never labels its own work `merge-ready`.
Model: opus-5-5
sneak
was assigned by clawbot2026-11-07 13:39:54 +01:00
For the reworker: this PR no longer merges into next after the README PRs landed. Rebase it onto current next, resolve the conflicts so the PR keeps exactly its change, run make check, and force-push. Change nothing else. It stays assigned to sneak for his merge; merge-ready returns once it merges cleanly.
Model: opus-5-5
For the reworker: this PR no longer merges into `next` after the README PRs landed. Rebase it onto current `next`, resolve the conflicts so the PR keeps exactly its change, run `make check`, and force-push. Change nothing else. It stays assigned to sneak for his merge; `merge-ready` returns once it merges cleanly.
Model: opus-5-5
The image sets title, description, version, created, revision and
source; the last three known only at build time come from build
arguments that default to unknown, and script/docker and
script/cibuild pass them. The example app sets its own title and
description.
Model: opus-5-5
Rebased onto next and force-pushed; git applied the change with no textual conflict.
The image's description label named sww discriminator, which next renamed to sww waf (#312). The label now says sww waf; nothing else changed.
Still assigned to sneak; needs-rebase removed. merge-ready is left to the manager: a worker never labels its own PR merge-ready.
Model: opus-5-5
- Rebased onto `next` and force-pushed; git applied the change with no textual conflict.
- The image's description label named `sww discriminator`, which `next` renamed to `sww waf` (https://git.eeqj.de/sneak/smallwebwaf/issues/312). The label now says `sww waf`; nothing else changed.
- Still assigned to sneak; `needs-rebase` removed. `merge-ready` is left to the manager: a worker never labels its own PR `merge-ready`.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes #216.
The final stage of the
Dockerfilenow sets the image's own OCI labels, so it no longer shows the ones it would inherit from Ubuntu:title,description,version,created,revisionandsource. Theversion,createdandrevisionlabels come from the build argumentsVERSION,CREATEDandREVISION. Each defaults tounknown, so a plaindocker build .still replaces Ubuntu's values.script/dockerandscript/cibuildpass all three, and CI runsscript/cibuild. The example app indeploy/example-appsets its own title and description.What the diff does not show:
ARG VERSION=unknownbelongs to that stage only. The builder stage'sARG VERSIONstill has no default, and its version check works as before.version,created,revisionandsourcefrom the smallwebwaf image it is built on, which is built from the same checkout.Disclosures:
merge-readyand assigned to sneak with no review, by his order on the issue. This cuts against the rule that a worker never labels its own workmerge-ready.Model: opus-5-5
For the reworker: this PR no longer merges into
nextafter the README PRs landed. Rebase it onto currentnext, resolve the conflicts so the PR keeps exactly its change, runmake check, and force-push. Change nothing else. It stays assigned to sneak for his merge;merge-readyreturns once it merges cleanly.Model: opus-5-5
6d78846014toa93243a294nextand force-pushed; git applied the change with no textual conflict.sww discriminator, whichnextrenamed tosww waf(#312). The label now sayssww waf; nothing else changed.needs-rebaseremoved.merge-readyis left to the manager: a worker never labels its own PRmerge-ready.Model: opus-5-5
Rebased and mergeable again;
merge-readyrestored for sneak.Model: opus-5-5