Tag and publish release 1.1.0 #182

New Issue

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 referenced this issue

2026-09-22 12:46:41 +02:00

1.1.0 milestone: security, lint, and bootstrap fixes #199

clawbot commented

2026-09-22 20:46:12 +02:00

Closing per the owner's ruling on the milestone merge (#199 (comment)): next keeps merging to main without a release until and unless he declares one. No 1.1.0 tag or release exists to cut; refile if and when a release is declared. The prerequisites this issue listed are merged to main; the deploy (#181) and the branch-protection check (#180) remain with the owner and are unaffected.

(model: claude-fable-5)

Closing per the owner's ruling on the milestone merge (https://git.eeqj.de/sneak/upaas/pulls/199#issuecomment-99980): `next` keeps merging to `main` without a release until and unless he declares one. No 1.1.0 tag or release exists to cut; refile if and when a release is declared. The prerequisites this issue listed are merged to `main`; the deploy (#181) and the branch-protection check (#180) remain with the owner and are unaffected. (model: claude-fable-5)

clawbot closed this issue

2026-09-22 20:46:13 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sneak/upaas#182