Tag and publish release 1.1.0 #182

New Issue

clawbot · 2026-08-07T18:41:25+02:00

clawbot commented

2026-08-07 18:41:25 +02:00

Cut the 1.1.0 release once the milestone's other issues are done.
SemVer minor: since 1.0.0, main gained GitHub and GitLab webhook
support (#170), per-app CPU/memory resource limits (#165), the
scripts-to-rule-them-all entrypoints (#174), plus the lint/security
cleanup tracked in this milestone.

Prerequisites (in order):

#175, #176, #177, #178 — make check clean under golangci-lint
≥ 2.12
#179 — CI lint pin bumped so the gate matches
#180 — branch protection verified
#181 — deployed and verified on fsn1app1

Steps:

update TODO.md Status section to reflect a green main and the
release
tag 1.1.0 on the verified main commit (the same commit deployed
in #181, or its descendant with no functional diff)
publish a Gitea release for the tag with notes summarizing the
changes since 1.0.0

Definition of done:

annotated tag 1.1.0 exists on main and is pushed
Gitea release published with release notes
make check green on the tagged commit; CI green on main

Cut the `1.1.0` release once the milestone's other issues are done. SemVer minor: since `1.0.0`, `main` gained GitHub and GitLab webhook support (#170), per-app CPU/memory resource limits (#165), the scripts-to-rule-them-all entrypoints (#174), plus the lint/security cleanup tracked in this milestone. Prerequisites (in order): - #175, #176, #177, #178 — `make check` clean under golangci-lint ≥ 2.12 - #179 — CI lint pin bumped so the gate matches - #180 — branch protection verified - #181 — deployed and verified on fsn1app1 Steps: - update `TODO.md` Status section to reflect a green `main` and the release - tag `1.1.0` on the verified `main` commit (the same commit deployed in #181, or its descendant with no functional diff) - publish a Gitea release for the tag with notes summarizing the changes since `1.0.0` Definition of done: - annotated tag `1.1.0` exists on `main` and is pushed - Gitea release published with release notes - `make check` green on the tagged commit; CI green on `main`

clawbot added this to the 1.1.0 milestone 2026-08-07 18:41:25 +02:00

clawbot commented

2026-09-03 18:29:27 +02:00

Prerequisite status refresh (2026-09-03) — not ready to tag

Re-checked every prerequisite listed above against main @ 7a34fc9. Note the ~90-day gap in agent activity on this repo (2026-06-05 to 2026-09-03); this is the first re-verification since.

Prereq	State
#175 noctx	✅ closed, PR #183
#176 gosec G710	✅ closed, PR #186
#177 gosec G703	❌ still open — suppressed with `#nosec`, not fixed; see my comment there
#178 goconst	✅ closed today, verified fixed by PR #187
#179 lint pin bump	✅ closed today, verified `v2.12.2` digest-pinned
#180 branch protection	⏸ blocked — needs repo admin, reassigned to @sneak
#181 deploy to fsn1app1	⏸ open, assigned @sneak (needs server access)

Also outstanding in the 1.1.0 milestone: #184 (bootstrap missing goimports) and #185 (vendored alpine.min.js un-minified on main — that one ships a 2x-size asset to users and should arguably block a release).

Good news: main is green. A full docker build . on 7a34fc9 passes end to end (exit 0) — make fmt-check, make lint (0 issues. under v2.12.2), make test, and the binary build.

Not proceeding autonomously

Tagging and publishing a release is an outward-facing, hard-to-reverse action, so no agent will do it without an explicit go-ahead. Four prerequisites are unmet regardless. @sneak — say the word once #177/#180/#181 are settled and I will queue the TODO.md + release-notes prep, but the tag and publish stay yours.

## Prerequisite status refresh (2026-09-03) — not ready to tag Re-checked every prerequisite listed above against `main` @ 7a34fc9. Note the ~90-day gap in agent activity on this repo (2026-06-05 to 2026-09-03); this is the first re-verification since. | Prereq | State | |---|---| | #175 noctx | ✅ closed, [PR #183](https://git.eeqj.de/sneak/upaas/pulls/183) | | #176 gosec G710 | ✅ closed, [PR #186](https://git.eeqj.de/sneak/upaas/pulls/186) | | [#177](https://git.eeqj.de/sneak/upaas/issues/177) gosec G703 | ❌ **still open** — suppressed with `#nosec`, not fixed; see my comment there | | [#178](https://git.eeqj.de/sneak/upaas/issues/178) goconst | ✅ closed today, verified fixed by [PR #187](https://git.eeqj.de/sneak/upaas/pulls/187) | | [#179](https://git.eeqj.de/sneak/upaas/issues/179) lint pin bump | ✅ closed today, verified `v2.12.2` digest-pinned | | [#180](https://git.eeqj.de/sneak/upaas/issues/180) branch protection | ⏸ blocked — needs repo admin, reassigned to @sneak | | [#181](https://git.eeqj.de/sneak/upaas/issues/181) deploy to fsn1app1 | ⏸ open, assigned @sneak (needs server access) | Also outstanding in the `1.1.0` milestone: [#184](https://git.eeqj.de/sneak/upaas/issues/184) (bootstrap missing `goimports`) and [#185](https://git.eeqj.de/sneak/upaas/issues/185) (vendored `alpine.min.js` un-minified on `main` — that one ships a 2x-size asset to users and should arguably block a release). Good news: **`main` is green.** A full `docker build .` on 7a34fc9 passes end to end (exit 0) — `make fmt-check`, `make lint` (`0 issues.` under v2.12.2), `make test`, and the binary build. ### Not proceeding autonomously Tagging and publishing a release is an outward-facing, hard-to-reverse action, so no agent will do it without an explicit go-ahead. Four prerequisites are unmet regardless. @sneak — say the word once #177/#180/#181 are settled and I will queue the `TODO.md` + release-notes prep, but the tag and publish stay yours.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sneak/upaas#182