Release: tag v1.0.0 on main once the milestone closes #112

Open
opened 2026-09-21 09:19:49 +02:00 by clawbot · 5 comments
Collaborator

Closing step for the 1.0.0 milestone. Filed now so the release has a definition of done and is not improvised on the day.

No git tag exists today. Makefile derives VERSION from git describe --tags --always --dirty, so untagged builds report a bare commit hash and the runtime image is tagged pixad:dev-style.

Definition of done

  1. Every issue on the 1.0.0 milestone is closed or explicitly moved to a later milestone by the owner.
  2. next has been merged to main by the owner via #105 and main is green (script/cibuild and make docker-smoke pass on the main head).
  3. TODO.md Status section says 1.0.0 is tagged and names the commit.
  4. The owner creates the annotated tag v1.0.0 on that main commit and pushes it. Tag creation and push are the owner's act; a worker prepares the TODO.md change as a PR and stops.
  5. make build on the tagged commit reports Version=v1.0.0; make docker-versioned produces pixad:v1.0.0.

model: claude-fable-5

Closing step for the `1.0.0` milestone. Filed now so the release has a definition of done and is not improvised on the day. No git tag exists today. `Makefile` derives `VERSION` from `git describe --tags --always --dirty`, so untagged builds report a bare commit hash and the runtime image is tagged `pixad:dev`-style. ## Definition of done 1. Every issue on the `1.0.0` milestone is closed or explicitly moved to a later milestone by the owner. 2. `next` has been merged to `main` by the owner via https://git.eeqj.de/sneak/pixa/pulls/105 and `main` is green (`script/cibuild` and `make docker-smoke` pass on the `main` head). 3. `TODO.md` Status section says 1.0.0 is tagged and names the commit. 4. The owner creates the annotated tag `v1.0.0` on that `main` commit and pushes it. Tag creation and push are the owner's act; a worker prepares the `TODO.md` change as a PR and stops. 5. `make build` on the tagged commit reports `Version=v1.0.0`; `make docker-versioned` produces `pixad:v1.0.0`. model: claude-fable-5
Author
Collaborator

pixa is a release candidate: v1.0.0-rc2 on next at afb5dc5 (https://git.eeqj.de/sneak/pixa/src/tag/v1.0.0-rc2). The final 1.0 is yours to validate and tag.

  • The one audit of v1.0.0-rc1 found a critical defect: a size with one side 0, or fit=outside, could make an output of unbounded size. rc2 refuses both with 400 (#241, #257).
  • Its other findings are open issues, none critical; the two rated high are #242 (memory per image in the container) and #254 (metrics labels grow without bound when metrics are on).
  • Open with you: #168, #180, #203.

Model: opus-5-5

pixa is a release candidate: `v1.0.0-rc2` on `next` at `afb5dc5` (https://git.eeqj.de/sneak/pixa/src/tag/v1.0.0-rc2). The final 1.0 is yours to validate and tag. - The one audit of `v1.0.0-rc1` found a critical defect: a size with one side `0`, or `fit=outside`, could make an output of unbounded size. rc2 refuses both with 400 (https://git.eeqj.de/sneak/pixa/issues/241, https://git.eeqj.de/sneak/pixa/issues/257). - Its other findings are open issues, none critical; the two rated high are https://git.eeqj.de/sneak/pixa/issues/242 (memory per image in the container) and https://git.eeqj.de/sneak/pixa/issues/254 (metrics labels grow without bound when metrics are on). - Open with you: https://git.eeqj.de/sneak/pixa/issues/168, https://git.eeqj.de/sneak/pixa/issues/180, https://git.eeqj.de/sneak/pixa/issues/203. Model: opus-5-5
sneak was assigned by clawbot 2026-10-13 10:57:05 +02:00
Author
Collaborator

Not a release candidate any more: sneak ruled that nothing can be a release candidate with known open bugs (sneak/project-management#32), and this repo's audit findings are still open. They get fixed when its manager slot comes; a new release-candidate tag follows only with no known bug open, and this comes back to sneak then. Reassigned to clawbot.

Model: opus-5-5

Not a release candidate any more: sneak ruled that nothing can be a release candidate with known open bugs (https://git.eeqj.de/sneak/project-management/issues/32), and this repo's audit findings are still open. They get fixed when its manager slot comes; a new release-candidate tag follows only with no known bug open, and this comes back to sneak then. Reassigned to clawbot. Model: opus-5-5
sneak was unassigned by clawbot 2026-10-14 19:53:23 +02:00
clawbot self-assigned this 2026-10-14 19:53:23 +02:00
Author
Collaborator

Handover (repo manager, 2026-10-16 04:55 UTC): not yet a release candidate; four known bugs are open. next is green at faad959.

Open bugs, each with its next step:

  • #301 (not started): a blocked_networks entry in the IPv4-mapped form is accepted but refuses nothing. Next: one worker on its definition of done (recommended: turn such an entry into the IPv4 range it covers), then a review, gate and squash-merge.
  • Waiting only on sneak approving a change to an existing test (asked as a standing rule on #280); on his yes, each goes to a rework worker, then a fresh review:

Every PR that lands needs a TODO.md-only rebase when another landed after its review, because Gitea does not apply the union merge TODO.md uses. When all open bugs are closed, next gets the next free v1.0.0-rcN tag (after v1.0.0-rc2) and this issue gets one short comment saying it is a release candidate with no known open bugs.

Model: opus-5-5

Handover (repo manager, 2026-10-16 04:55 UTC): not yet a release candidate; four known bugs are open. `next` is green at `faad959`. Open bugs, each with its next step: - https://git.eeqj.de/sneak/pixa/issues/301 (not started): a `blocked_networks` entry in the IPv4-mapped form is accepted but refuses nothing. Next: one worker on its definition of done (recommended: turn such an entry into the IPv4 range it covers), then a review, gate and squash-merge. - Waiting only on sneak approving a change to an existing test (asked as a standing rule on https://git.eeqj.de/sneak/pixa/issues/280); on his yes, each goes to a rework worker, then a fresh review: - https://git.eeqj.de/sneak/pixa/issues/250 → https://git.eeqj.de/sneak/pixa/pulls/279 (red until two tests change; question https://git.eeqj.de/sneak/pixa/pulls/279#issuecomment-143984) - https://git.eeqj.de/sneak/pixa/issues/253 → https://git.eeqj.de/sneak/pixa/pulls/273 (question https://git.eeqj.de/sneak/pixa/issues/253#issuecomment-142424) - https://git.eeqj.de/sneak/pixa/issues/272 → https://git.eeqj.de/sneak/pixa/pulls/278 (question https://git.eeqj.de/sneak/pixa/pulls/278#issuecomment-143931; the three small findings in https://git.eeqj.de/sneak/pixa/pulls/278#issuecomment-144377 are held for that answer, then one rework and a rebase) Every PR that lands needs a `TODO.md`-only rebase when another landed after its review, because Gitea does not apply the union merge `TODO.md` uses. When all open bugs are closed, `next` gets the next free `v1.0.0-rcN` tag (after `v1.0.0-rc2`) and this issue gets one short comment saying it is a release candidate with no known open bugs. Model: opus-5-5
Author
Collaborator

Repo manager state, 2026-10-20: done. v1.0.0-rc3 is tagged on next at 989da78 with no known open bugs; see the comment below. Open issues are assigned to sneak or set for 1.1.

Model: opus-5-5

Repo manager state, 2026-10-20: done. `v1.0.0-rc3` is tagged on `next` at `989da78` with no known open bugs; see the comment below. Open issues are assigned to sneak or set for 1.1. Model: opus-5-5
Author
Collaborator

pixa is a release candidate with no known open bugs: v1.0.0-rc3 on next at 989da78 (https://git.eeqj.de/sneak/pixa/src/tag/v1.0.0-rc3). The last bugs closed are #272 (#278) and #253 (#273), with the rule from #280 now in AGENTS.md. The final 1.0 is yours to validate and tag.

Model: opus-5-5

pixa is a release candidate with no known open bugs: `v1.0.0-rc3` on `next` at `989da78` (https://git.eeqj.de/sneak/pixa/src/tag/v1.0.0-rc3). The last bugs closed are https://git.eeqj.de/sneak/pixa/issues/272 (https://git.eeqj.de/sneak/pixa/pulls/278) and https://git.eeqj.de/sneak/pixa/issues/253 (https://git.eeqj.de/sneak/pixa/pulls/273), with the rule from https://git.eeqj.de/sneak/pixa/issues/280 now in `AGENTS.md`. The final 1.0 is yours to validate and tag. Model: opus-5-5
clawbot removed their assignment 2026-10-20 19:53:44 +02:00
sneak was assigned by clawbot 2026-10-20 19:53:44 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/pixa#112