sneak/quak
1
0
Fork 0
Code Issues 8 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

Tag v1.0.0 #15

New Issue
Closed
opened 2026-08-09 03:46:09 +02:00 by clawbot · 2 comments
clawbot commented 2026-08-09 03:46:09 +02:00
Collaborator
Copy Link
Copy Source

Goal

Cut the first release. This is the last issue in the 1.0.0 milestone and must not be started
until every other issue in that milestone is closed.

Definition of done

  1. Every other issue in the 1.0.0 milestone is closed.
  2. main is green: make check and make docker both pass on a clean checkout.
  3. The version is bumped to 1.0.0 in the single place the version now lives, and VERSION,
    quak --version and package.json all agree (enforced by the test added for that).
  4. The README TODO section reflects reality: every pre-1.0 box ticked or moved to the future
    section, and the "Tag v1.0.0" box ticked.
  5. TODO.md Status is no longer pre-1.0, the completed steps list is current, and the
    remaining Future Steps are only the post-1.0 desktop-client items.
  6. An annotated tag v1.0.0 exists on the release commit and is pushed.
  7. A Gitea release is created for the tag with notes summarising what 1.0.0 contains.
  8. The 1.0.0 milestone is closed.

Notes

Whether a published npm package accompanies the tag depends on the outcome of the npm
publishing decision issue. If that is answered "yes", the publish happens as part of this
issue; if "no", the tag stands alone.

## Goal Cut the first release. This is the last issue in the `1.0.0` milestone and must not be started until every other issue in that milestone is closed. ## Definition of done 1. Every other issue in the `1.0.0` milestone is closed. 2. `main` is green: `make check` and `make docker` both pass on a clean checkout. 3. The version is bumped to `1.0.0` in the single place the version now lives, and `VERSION`, `quak --version` and `package.json` all agree (enforced by the test added for that). 4. The README TODO section reflects reality: every pre-1.0 box ticked or moved to the future section, and the "Tag `v1.0.0`" box ticked. 5. `TODO.md` Status is no longer `pre-1.0`, the completed steps list is current, and the remaining Future Steps are only the post-1.0 desktop-client items. 6. An annotated tag `v1.0.0` exists on the release commit and is pushed. 7. A Gitea release is created for the tag with notes summarising what 1.0.0 contains. 8. The `1.0.0` milestone is closed. ## Notes Whether a published npm package accompanies the tag depends on the outcome of the npm publishing decision issue. If that is answered "yes", the publish happens as part of this issue; if "no", the tag stands alone.
clawbot added this to the 1.0.0 milestone 2026-08-09 03:46:09 +02:00
clawbot self-assigned this 2026-08-09 03:46:09 +02:00
clawbot commented 2026-08-09 03:47:27 +02:00
Author
Collaborator
Copy Link
Copy Source

Manager note: pre-1.0 backlog and ordering

Backlog filed 2026-08-09 after a full read of TODO.md, README.md, REPO_POLICIES.md, the
org code standards in the prompts repo, and a line-by-line survey of src/, bin/,
test/, script/, and the container/CI files. make check was green on main at 2039608
(17 files, 120 tests) before any of this work started.

Fifteen issues carry the 1.0.0 milestone. Intended order, driven by dependency rather than
severity:

  1. #1 — download truncation detection and atomic writes. Prerequisite for #2 and #8.
  2. #2 — retry policy. The declared TODO.md Next Step.
  3. #3 — fix the TypeScript build. make build fails on main today; #5 and #6 both depend on
    the resulting dist/ layout.
  4. #4 — make docker green. Depends on #3.
  5. #6 — package metadata. Settles which symbols are public, which #13 needs.
  6. #5 — single-source the version string.
  7. #13 — rewrite the README API reference. Depends on #6.
  8. #7, #8, #9, #10, #11, #12 — correctness, security and coverage work; independent of each
    other and can interleave with the above.
  9. #14 — blocked on your decision.
  10. #15 — this issue, last.

Outside the milestone: #16 (npm decision, yours), #17, #18, #19.

Org standard check: .golangci.yml

Verified not applicable. quak contains zero Go files — no *.go, no go.mod, no
.golangci.yml — so the org-standard linter config and its pinned golangci-lint version have
nothing to apply to here. The JavaScript toolchain equivalents (eslint.config.mjs,
.prettierrc with 4-space tabs and proseWrap: always) are present and make lint and
make fmt-check are both green. No issue filed.

Vendored policy file

REPO_POLICIES.md in this repo is byte-identical to the current authoritative copy in the
prompts repo. Nothing to refresh.

## Manager note: pre-1.0 backlog and ordering Backlog filed 2026-08-09 after a full read of `TODO.md`, `README.md`, `REPO_POLICIES.md`, the org code standards in the `prompts` repo, and a line-by-line survey of `src/`, `bin/`, `test/`, `script/`, and the container/CI files. `make check` was green on `main` at `2039608` (17 files, 120 tests) before any of this work started. Fifteen issues carry the `1.0.0` milestone. Intended order, driven by dependency rather than severity: 1. #1 — download truncation detection and atomic writes. Prerequisite for #2 and #8. 2. #2 — retry policy. The declared `TODO.md` Next Step. 3. #3 — fix the TypeScript build. `make build` fails on `main` today; #5 and #6 both depend on the resulting `dist/` layout. 4. #4 — `make docker` green. Depends on #3. 5. #6 — package metadata. Settles which symbols are public, which #13 needs. 6. #5 — single-source the version string. 7. #13 — rewrite the README API reference. Depends on #6. 8. #7, #8, #9, #10, #11, #12 — correctness, security and coverage work; independent of each other and can interleave with the above. 9. #14 — blocked on your decision. 10. #15 — this issue, last. Outside the milestone: #16 (npm decision, yours), #17, #18, #19. ## Org standard check: `.golangci.yml` Verified not applicable. quak contains zero Go files — no `*.go`, no `go.mod`, no `.golangci.yml` — so the org-standard linter config and its pinned golangci-lint version have nothing to apply to here. The JavaScript toolchain equivalents (`eslint.config.mjs`, `.prettierrc` with 4-space tabs and `proseWrap: always`) are present and `make lint` and `make fmt-check` are both green. No issue filed. ## Vendored policy file `REPO_POLICIES.md` in this repo is byte-identical to the current authoritative copy in the `prompts` repo. Nothing to refresh.
clawbot commented 2026-09-23 01:36:26 +02:00
Author
Collaborator
Copy Link
Copy Source

Closed by the top-level manager. sneak ruled on 2026-09-22 (sneak/upaas#199 (comment)) that merging next into main is not a release, and that there is no release until he declares one. Tag and release issues are not kept open without that declaration; upaas issue 182 was closed on the same ruling. A new issue is filed if he declares a release.

Model: opus-5-5

Closed by the top-level manager. sneak ruled on 2026-09-22 (https://git.eeqj.de/sneak/upaas/pulls/199#issuecomment-99980) that merging `next` into `main` is not a release, and that there is no release until he declares one. Tag and release issues are not kept open without that declaration; upaas issue 182 was closed on the same ruling. A new issue is filed if he declares a release. Model: opus-5-5
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
merge-ready
Review passed; ready to merge
 needs-checks
CI / make check is not green on this PR
 needs-rebase
PR conflicts with main and must be rebased
 needs-review
PR is awaiting adversarial review
 needs-rework
Review failed; PR needs changes
No labels
Milestone
No items
No Milestone 1.0.0
Projects
Clear projects
No projects
Assignees
Clear assignees
clawbot sneak (Jeffrey Paul)
No Assignees clawbot
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/quak#15