From 5976ac1fdfbf267677e32e48dc938b7edf0f6af8 Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Tue, 17 Nov 2026 08:49:28 +0000 Subject: [PATCH 1/9] chore: move repo config under .dz/ --- .dz/maintainer/maintainer.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/.dz/maintainer/maintainer.yml b/.dz/maintainer/maintainer.yml index 8813034..e240310 100644 --- a/.dz/maintainer/maintainer.yml +++ b/.dz/maintainer/maintainer.yml @@ -145,19 +145,19 @@ schedules: - name: release-due days: [tue] hours_utc: [3] - brief_file: .dz/briefs/release-due.md + brief_file: .dz/schedules/release-due.md # The one exception, so a confirmed security fix does not wait up to a week for the slot above. - name: security-release days: [mon, wed, thu, fri, sat, sun] hours_utc: [6] - brief_file: .dz/briefs/security-release.md + brief_file: .dz/schedules/security-release.md # Weekly: the failures nothing announces. - name: health days: [tue] hours_utc: [7] - brief_file: .dz/briefs/health.md + brief_file: .dz/schedules/health.md # Monthly: fires every Tuesday and the brief acts only on the first Tuesday of the month. - name: improve days: [tue] hours_utc: [8] - brief_file: .dz/briefs/improve.md + brief_file: .dz/schedules/improve.md From 066ec15de33a6494787a87917163064f21b39b8d Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Tue, 17 Nov 2026 08:49:29 +0000 Subject: [PATCH 2/9] chore: move repo config under .dz/ --- .dz/schedules/health.md | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 .dz/schedules/health.md diff --git a/.dz/schedules/health.md b/.dz/schedules/health.md new file mode 100644 index 0000000..0313ec5 --- /dev/null +++ b/.dz/schedules/health.md @@ -0,0 +1,38 @@ +# Brief: is the project healthy? + +Weekly checkup (Tuesdays 07:00 UTC) fired by `schedules: health`: the failures no issue or PR announces. + +| Signal | Command | Healthy | +|---|---|---| +| `main` is green | `gh run list --workflow ci.yml --branch main --event push --limit 1 --json conclusion,headSha,url`, then `git rev-parse origin/main` | `success` on the `origin/main` tip; a null conclusion or another sha is no verdict | +| the last tag published | `t=$(git describe --tags --abbrev=0 --match 'v[0-9]*' origin/main); gh run list --workflow ci.yml --event push --limit 20 --json conclusion,headSha,headBranch,url` filtered to `headBranch == $t` | `success`; no run for that tag is no verdict | +| the stamped version is tagged | `grep -m1 '^version' Cargo.toml` against `$t` | equal, or an open release PR or in-flight run explains it | +| the GitHub Release exists with its assets | `gh release view "$t" --json isDraft,publishedAt,assets` | not a draft, published, carrying both `.deb` files and `SHA256SUMS` (`deploy/install.sh` refuses a release without them) | +| the image is pullable | `docker manifest inspect ghcr.io/developerz-ai/mcp-ssh:${t#v}` | lists `linux/amd64` and `linux/arm64` | +| Dependabot is not stuck | `gh pr list --app dependabot --state open --limit 100 --json number,updatedAt,statusCheckRollup` | no PR with failed checks and more than 7 days since `updatedAt` | +| no stale toolchain | `rust-toolchain.toml` channel, `Cargo.toml` `rust-version` and the Dockerfile `FROM` | all three name the same version (CLAUDE.md: bump together) | + +## What to file + +For each unhealthy signal, one ask, unless an open issue already carries its exact title. Read the +open titles first, exactly so: `gh api --paginate "repos/developerz-ai/mcp-ssh/issues?state=open" | jq -r '.[] | select(.pull_request == null) | .title'`, +then compare byte for byte. A failed read is no verdict, never "no open ask". +Titles are stable: nothing that changes run to run (sha, run URL, version) goes in one; that goes in the body, +with the command and its output. Unreadable evidence is no verdict: re-run it, never file it as a defect. +A red `main` comes first: nothing releases from it. + +A drifted toolchain is fixable by the fleet: the ask says to bump all three pins to the newest stable +Rust that is at least 14 days old in one PR, fixing any new clippy lint under `-D warnings`. + +This lane reads and files; it never repairs. It never re-runs a publish, re-tags, moves or deletes a tag, +pushes an image by hand, force-pushes `main` or merges with `--admin`. + +## Rows + +- `main-green` — The latest `ci.yml` push run on the `origin/main` tip is `success`. +- `last-tag-published` — The last `v*` tag has a `success` `ci.yml` run. +- `stamped-version-tagged` — `version` in `Cargo.toml` equals that tag, or a release in flight explains it. +- `github-release-published` — The GitHub Release for that tag is published with both `.deb` files and `SHA256SUMS`. +- `image-pullable` — The GHCR image for that tag lists amd64 and arm64. +- `dependabot-not-stuck` — No open Dependabot PR has failed checks with more than 7 days since its `updatedAt`. +- `toolchain-in-step` — `rust-toolchain.toml`, `Cargo.toml` `rust-version` and the Dockerfile base agree. From fe0085962189d63b528186f92af9f746b6a913dc Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Tue, 17 Nov 2026 08:49:31 +0000 Subject: [PATCH 3/9] chore: move repo config under .dz/ --- .dz/briefs/health.md | 38 -------------------------------------- 1 file changed, 38 deletions(-) delete mode 100644 .dz/briefs/health.md diff --git a/.dz/briefs/health.md b/.dz/briefs/health.md deleted file mode 100644 index 0313ec5..0000000 --- a/.dz/briefs/health.md +++ /dev/null @@ -1,38 +0,0 @@ -# Brief: is the project healthy? - -Weekly checkup (Tuesdays 07:00 UTC) fired by `schedules: health`: the failures no issue or PR announces. - -| Signal | Command | Healthy | -|---|---|---| -| `main` is green | `gh run list --workflow ci.yml --branch main --event push --limit 1 --json conclusion,headSha,url`, then `git rev-parse origin/main` | `success` on the `origin/main` tip; a null conclusion or another sha is no verdict | -| the last tag published | `t=$(git describe --tags --abbrev=0 --match 'v[0-9]*' origin/main); gh run list --workflow ci.yml --event push --limit 20 --json conclusion,headSha,headBranch,url` filtered to `headBranch == $t` | `success`; no run for that tag is no verdict | -| the stamped version is tagged | `grep -m1 '^version' Cargo.toml` against `$t` | equal, or an open release PR or in-flight run explains it | -| the GitHub Release exists with its assets | `gh release view "$t" --json isDraft,publishedAt,assets` | not a draft, published, carrying both `.deb` files and `SHA256SUMS` (`deploy/install.sh` refuses a release without them) | -| the image is pullable | `docker manifest inspect ghcr.io/developerz-ai/mcp-ssh:${t#v}` | lists `linux/amd64` and `linux/arm64` | -| Dependabot is not stuck | `gh pr list --app dependabot --state open --limit 100 --json number,updatedAt,statusCheckRollup` | no PR with failed checks and more than 7 days since `updatedAt` | -| no stale toolchain | `rust-toolchain.toml` channel, `Cargo.toml` `rust-version` and the Dockerfile `FROM` | all three name the same version (CLAUDE.md: bump together) | - -## What to file - -For each unhealthy signal, one ask, unless an open issue already carries its exact title. Read the -open titles first, exactly so: `gh api --paginate "repos/developerz-ai/mcp-ssh/issues?state=open" | jq -r '.[] | select(.pull_request == null) | .title'`, -then compare byte for byte. A failed read is no verdict, never "no open ask". -Titles are stable: nothing that changes run to run (sha, run URL, version) goes in one; that goes in the body, -with the command and its output. Unreadable evidence is no verdict: re-run it, never file it as a defect. -A red `main` comes first: nothing releases from it. - -A drifted toolchain is fixable by the fleet: the ask says to bump all three pins to the newest stable -Rust that is at least 14 days old in one PR, fixing any new clippy lint under `-D warnings`. - -This lane reads and files; it never repairs. It never re-runs a publish, re-tags, moves or deletes a tag, -pushes an image by hand, force-pushes `main` or merges with `--admin`. - -## Rows - -- `main-green` — The latest `ci.yml` push run on the `origin/main` tip is `success`. -- `last-tag-published` — The last `v*` tag has a `success` `ci.yml` run. -- `stamped-version-tagged` — `version` in `Cargo.toml` equals that tag, or a release in flight explains it. -- `github-release-published` — The GitHub Release for that tag is published with both `.deb` files and `SHA256SUMS`. -- `image-pullable` — The GHCR image for that tag lists amd64 and arm64. -- `dependabot-not-stuck` — No open Dependabot PR has failed checks with more than 7 days since its `updatedAt`. -- `toolchain-in-step` — `rust-toolchain.toml`, `Cargo.toml` `rust-version` and the Dockerfile base agree. From 163325488eb16e48e203917ba49d21c2c6a127e1 Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Tue, 17 Nov 2026 08:49:32 +0000 Subject: [PATCH 4/9] chore: move repo config under .dz/ --- .dz/schedules/improve.md | 45 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 45 insertions(+) create mode 100644 .dz/schedules/improve.md diff --git a/.dz/schedules/improve.md b/.dz/schedules/improve.md new file mode 100644 index 0000000..ff9244c --- /dev/null +++ b/.dz/schedules/improve.md @@ -0,0 +1,45 @@ +# Brief: monthly improvement + +Fired every Tuesday by `schedules: improve`. **Act only on the first Tuesday of the month:** +`[ "$(date -u +%-d)" -le 7 ]`. On any other Tuesday stop here, file nothing, open nothing. + +Once a month, leave mcp-ssh measurably better, so nobody has to touch it by hand. `CLAUDE.md` binds every change, and `non_goals` in the policy file are off limits. A red `main`, a missing publish and a stuck Dependabot PR belong to `health`. + +## Signals + +| Signal | Command | +|---|---| +| the gate on fresh `main` | `bin/check` | +| advisories | `cargo audit` | +| dependency majors | `cargo outdated` if installed, else the Dependabot PRs closed red | +| the Rust toolchain | newest stable Rust at least 14 days old, against `rust-toolchain.toml` | +| open bugs | `gh issue list --state open --label bug --json number,title,url` | +| deep read | `.dz/schedules/hygiene.md` and `.dz/schedules/devops.md`: what to look for, and the evidence rules | + +Read a failing job's log before deciding anything. A red run whose log names a missing secret or a repository setting is the owner's to fix: escalate once, never delete the check or turn it into a green skip. + +## Pick at most three, in this order + +1. Anything the gate found broken or flaky: the root cause, never a retry or a skip. +2. Advisories, then dependency majors Dependabot could not land (rmcp, axum, rusqlite), one per PR. +3. The toolchain, when more than one stable release behind: `rust-toolchain.toml`, `Cargo.toml` `rust-version` and the Dockerfile `FROM` together, new clippy lints fixed. Dependabot cannot do this (it ignores the cargo-chef base on purpose). +4. Open bugs, each starting from a test that fails on `main`. +5. Docs drift: README, CLAUDE.md (the module map, the tool table), `docs/`; quote the doc line and the code. +6. Hidden failures: an `|| true`, a `2>/dev/null`, a `continue-on-error`, an `.ok()` or `let _ =` that drops an error. Make it fail, or handle it visibly. A documented, deliberate fallback stays. +7. Simplification: dead code, duplicated logic, a file past the 300-LOC cap, slow or flaky tests. + +## Ship + +One small PR per improvement, its evidence in the body, `bin/check` green first, a line in `docs/changelog/unreleased.md` when users see it. Never bump the version, and never touch release automation from this checkup: open an issue instead. A breaking change is never merged by this lane (`escalate.ask_before_acting: [breaking_change]`): open the PR or issue and leave it for a maintainer. +Check no open PR or issue already covers it. If nothing is worth changing, do nothing: no empty PRs, no churn. + +## Rows + +- `gate`: `bin/check` on fresh `main` finds something broken or flaky; root cause, never a retry or a skip. +- `advisories`: `cargo audit` finds advisories; one per PR, before majors. +- `dependency-majors`: majors Dependabot could not land; one per PR. +- `toolchain`: the three Rust pins bumped together when behind. +- `open-bugs`: each from a test that fails on `main`. +- `docs-drift`: a doc line the code contradicts. +- `hidden-failures`: swallowed errors and CI skips, made visible. +- `simplification`: dead code, duplicated logic, files past 300 LOC, slow or flaky tests. From 3920025677be28e277aad41210d76c72f062389d Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Tue, 17 Nov 2026 08:49:33 +0000 Subject: [PATCH 5/9] chore: move repo config under .dz/ --- .dz/briefs/improve.md | 45 ------------------------------------------- 1 file changed, 45 deletions(-) delete mode 100644 .dz/briefs/improve.md diff --git a/.dz/briefs/improve.md b/.dz/briefs/improve.md deleted file mode 100644 index ff9244c..0000000 --- a/.dz/briefs/improve.md +++ /dev/null @@ -1,45 +0,0 @@ -# Brief: monthly improvement - -Fired every Tuesday by `schedules: improve`. **Act only on the first Tuesday of the month:** -`[ "$(date -u +%-d)" -le 7 ]`. On any other Tuesday stop here, file nothing, open nothing. - -Once a month, leave mcp-ssh measurably better, so nobody has to touch it by hand. `CLAUDE.md` binds every change, and `non_goals` in the policy file are off limits. A red `main`, a missing publish and a stuck Dependabot PR belong to `health`. - -## Signals - -| Signal | Command | -|---|---| -| the gate on fresh `main` | `bin/check` | -| advisories | `cargo audit` | -| dependency majors | `cargo outdated` if installed, else the Dependabot PRs closed red | -| the Rust toolchain | newest stable Rust at least 14 days old, against `rust-toolchain.toml` | -| open bugs | `gh issue list --state open --label bug --json number,title,url` | -| deep read | `.dz/schedules/hygiene.md` and `.dz/schedules/devops.md`: what to look for, and the evidence rules | - -Read a failing job's log before deciding anything. A red run whose log names a missing secret or a repository setting is the owner's to fix: escalate once, never delete the check or turn it into a green skip. - -## Pick at most three, in this order - -1. Anything the gate found broken or flaky: the root cause, never a retry or a skip. -2. Advisories, then dependency majors Dependabot could not land (rmcp, axum, rusqlite), one per PR. -3. The toolchain, when more than one stable release behind: `rust-toolchain.toml`, `Cargo.toml` `rust-version` and the Dockerfile `FROM` together, new clippy lints fixed. Dependabot cannot do this (it ignores the cargo-chef base on purpose). -4. Open bugs, each starting from a test that fails on `main`. -5. Docs drift: README, CLAUDE.md (the module map, the tool table), `docs/`; quote the doc line and the code. -6. Hidden failures: an `|| true`, a `2>/dev/null`, a `continue-on-error`, an `.ok()` or `let _ =` that drops an error. Make it fail, or handle it visibly. A documented, deliberate fallback stays. -7. Simplification: dead code, duplicated logic, a file past the 300-LOC cap, slow or flaky tests. - -## Ship - -One small PR per improvement, its evidence in the body, `bin/check` green first, a line in `docs/changelog/unreleased.md` when users see it. Never bump the version, and never touch release automation from this checkup: open an issue instead. A breaking change is never merged by this lane (`escalate.ask_before_acting: [breaking_change]`): open the PR or issue and leave it for a maintainer. -Check no open PR or issue already covers it. If nothing is worth changing, do nothing: no empty PRs, no churn. - -## Rows - -- `gate`: `bin/check` on fresh `main` finds something broken or flaky; root cause, never a retry or a skip. -- `advisories`: `cargo audit` finds advisories; one per PR, before majors. -- `dependency-majors`: majors Dependabot could not land; one per PR. -- `toolchain`: the three Rust pins bumped together when behind. -- `open-bugs`: each from a test that fails on `main`. -- `docs-drift`: a doc line the code contradicts. -- `hidden-failures`: swallowed errors and CI skips, made visible. -- `simplification`: dead code, duplicated logic, files past 300 LOC, slow or flaky tests. From 81e75101c6b338938a9c43eeb04551fd275acea5 Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Tue, 17 Nov 2026 08:49:34 +0000 Subject: [PATCH 6/9] chore: move repo config under .dz/ --- .dz/schedules/release-due.md | 53 ++++++++++++++++++++++++++++++++++++ 1 file changed, 53 insertions(+) create mode 100644 .dz/schedules/release-due.md diff --git a/.dz/schedules/release-due.md b/.dz/schedules/release-due.md new file mode 100644 index 0000000..94f7c80 --- /dev/null +++ b/.dz/schedules/release-due.md @@ -0,0 +1,53 @@ +# Brief: is a release needed? + +Weekly checkup, Tuesdays 03:00 UTC, fired by `schedules: release-due`. It covers what people install: the `v*` tag, the image on GHCR (`ghcr.io/developerz-ai/mcp-ssh`), and the GitHub Release carrying the `.deb` files that `deploy/install.sh` downloads. The block below gathers facts and you make the call. A merge or a count never cuts a release. + +## Judge + +Read everything merged since the last release: the window below with its diffs, then `git log "$last"..origin/main` for what the pathspec leaves out, and `docs/changelog/unreleased.md`. Does someone running mcp-ssh get something real from a release now? + +- Usually yes: a fix they can hit, a feature they can use, a dependency change that reaches the binary. +- Usually no: a run of dev-dependency or CI bumps. + +Nothing real: no release. Say why either way: a release ask opens with your reason, and a no ends your run summary with `no release: `. + +## Decide + +```bash +git fetch --tags --unshallow origin 2>/dev/null || git fetch --tags origin +last=$(git describe --tags --abbrev=0 --match 'v[0-9]*' origin/main) +git log --format='%h %cI %s' "$last"..origin/main -- src Cargo.toml Cargo.lock Dockerfile deploy/debian deploy/mcp-ssh.service +grep -m1 '^version' Cargo.toml +``` + +The pathspec names what ships in the binary, the image and the `.deb`. `deploy/install.sh` is served from `main` directly and needs no release. + +| Window | Do | +|---|---| +| a command above failed | no verdict: surface it, file nothing | +| empty | nothing | +| the stamped version is already ahead of `$last` | nothing: a release is in flight, watch `ci.yml` on the tag | +| the oldest shipping commit is under 24 h old | usually nothing: next week's checkup sees it | +| `main`'s latest `ci.yml` push run is not `success` | nothing: `health` owns a red `main` | +| a breaking change in the window | no release ask. If no open issue titled `Major release pending` exists, file one for a maintainer, with no release steps | +| otherwise | judge it above; when a release is needed, one ask, **Release ``**, listing the commits | + +``: a `feat` subject in the window is a minor, anything else a patch. + +## The ask + +Pre-flight guard: only a lane where `gh auth status` exits 0 files the ask. File nothing if an open issue title from `gh api --paginate "repos/developerz-ai/mcp-ssh/issues?state=open" | jq -r '.[] | select(.pull_request == null) | .title'` is exactly `Release `, or an open PR title from `gh api --paginate "repos/developerz-ai/mcp-ssh/pulls?state=open" | jq -r '.[].title'` matches `^chore\(release\):`. A failed read is no verdict. Body, for the box that takes it: + +1. Re-run Decide on fresh `main`; still needed, or stop. +2. Bump `version` in `Cargo.toml`, run `cargo update -p mcp-ssh` so `Cargo.lock` carries it. Move `docs/changelog/unreleased.md`'s entries to a new `docs/changelog/.md`, reset `unreleased.md` to its heading, and add the `## [] - ` entry at the top of `CHANGELOG.md` (one paragraph, linking the notes; update the `[Unreleased]` diff link). No source change. +3. `bin/check`, then one PR titled `chore(release): `. It merges on green like any PR, never `--admin`. +4. After it merges: `git fetch origin`, confirm `git show :Cargo.toml` shows ``, then `git tag -a v -m "v" && git push origin v`. +5. Watch `ci.yml` on the tag to the end: `version` (tag = Cargo.toml), the per-arch image smoke and push, `image-publish` (the multi-arch tag on GHCR), `deb`, then `release` (the GitHub Release with the `.deb` files and `SHA256SUMS`). A failure is an issue for a maintainer. + +Never re-tag, move or delete a tag, never force-push `main`, and never publish by hand. A failed publish ships its fix as the next patch. + +## Rows + +- `release-needed` — A release is needed now and none is in flight. +- `major-release-pending` — A breaking change is in the window and no open `Major release pending` issue exists. +- `release-publish-failed` — `ci.yml` on the tag was watched to the end and the publish failed. From e1109c01d9db9fd4769fa97f3c17fbf0496fd69b Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Tue, 17 Nov 2026 08:49:36 +0000 Subject: [PATCH 7/9] chore: move repo config under .dz/ --- .dz/briefs/release-due.md | 53 --------------------------------------- 1 file changed, 53 deletions(-) delete mode 100644 .dz/briefs/release-due.md diff --git a/.dz/briefs/release-due.md b/.dz/briefs/release-due.md deleted file mode 100644 index 94f7c80..0000000 --- a/.dz/briefs/release-due.md +++ /dev/null @@ -1,53 +0,0 @@ -# Brief: is a release needed? - -Weekly checkup, Tuesdays 03:00 UTC, fired by `schedules: release-due`. It covers what people install: the `v*` tag, the image on GHCR (`ghcr.io/developerz-ai/mcp-ssh`), and the GitHub Release carrying the `.deb` files that `deploy/install.sh` downloads. The block below gathers facts and you make the call. A merge or a count never cuts a release. - -## Judge - -Read everything merged since the last release: the window below with its diffs, then `git log "$last"..origin/main` for what the pathspec leaves out, and `docs/changelog/unreleased.md`. Does someone running mcp-ssh get something real from a release now? - -- Usually yes: a fix they can hit, a feature they can use, a dependency change that reaches the binary. -- Usually no: a run of dev-dependency or CI bumps. - -Nothing real: no release. Say why either way: a release ask opens with your reason, and a no ends your run summary with `no release: `. - -## Decide - -```bash -git fetch --tags --unshallow origin 2>/dev/null || git fetch --tags origin -last=$(git describe --tags --abbrev=0 --match 'v[0-9]*' origin/main) -git log --format='%h %cI %s' "$last"..origin/main -- src Cargo.toml Cargo.lock Dockerfile deploy/debian deploy/mcp-ssh.service -grep -m1 '^version' Cargo.toml -``` - -The pathspec names what ships in the binary, the image and the `.deb`. `deploy/install.sh` is served from `main` directly and needs no release. - -| Window | Do | -|---|---| -| a command above failed | no verdict: surface it, file nothing | -| empty | nothing | -| the stamped version is already ahead of `$last` | nothing: a release is in flight, watch `ci.yml` on the tag | -| the oldest shipping commit is under 24 h old | usually nothing: next week's checkup sees it | -| `main`'s latest `ci.yml` push run is not `success` | nothing: `health` owns a red `main` | -| a breaking change in the window | no release ask. If no open issue titled `Major release pending` exists, file one for a maintainer, with no release steps | -| otherwise | judge it above; when a release is needed, one ask, **Release ``**, listing the commits | - -``: a `feat` subject in the window is a minor, anything else a patch. - -## The ask - -Pre-flight guard: only a lane where `gh auth status` exits 0 files the ask. File nothing if an open issue title from `gh api --paginate "repos/developerz-ai/mcp-ssh/issues?state=open" | jq -r '.[] | select(.pull_request == null) | .title'` is exactly `Release `, or an open PR title from `gh api --paginate "repos/developerz-ai/mcp-ssh/pulls?state=open" | jq -r '.[].title'` matches `^chore\(release\):`. A failed read is no verdict. Body, for the box that takes it: - -1. Re-run Decide on fresh `main`; still needed, or stop. -2. Bump `version` in `Cargo.toml`, run `cargo update -p mcp-ssh` so `Cargo.lock` carries it. Move `docs/changelog/unreleased.md`'s entries to a new `docs/changelog/.md`, reset `unreleased.md` to its heading, and add the `## [] - ` entry at the top of `CHANGELOG.md` (one paragraph, linking the notes; update the `[Unreleased]` diff link). No source change. -3. `bin/check`, then one PR titled `chore(release): `. It merges on green like any PR, never `--admin`. -4. After it merges: `git fetch origin`, confirm `git show :Cargo.toml` shows ``, then `git tag -a v -m "v" && git push origin v`. -5. Watch `ci.yml` on the tag to the end: `version` (tag = Cargo.toml), the per-arch image smoke and push, `image-publish` (the multi-arch tag on GHCR), `deb`, then `release` (the GitHub Release with the `.deb` files and `SHA256SUMS`). A failure is an issue for a maintainer. - -Never re-tag, move or delete a tag, never force-push `main`, and never publish by hand. A failed publish ships its fix as the next patch. - -## Rows - -- `release-needed` — A release is needed now and none is in flight. -- `major-release-pending` — A breaking change is in the window and no open `Major release pending` issue exists. -- `release-publish-failed` — `ci.yml` on the tag was watched to the end and the publish failed. From 7f304886a6bf7055aa8fcdd7d5a15c90dccd3939 Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Tue, 17 Nov 2026 08:49:37 +0000 Subject: [PATCH 8/9] chore: move repo config under .dz/ --- .dz/schedules/security-release.md | 32 +++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 .dz/schedules/security-release.md diff --git a/.dz/schedules/security-release.md b/.dz/schedules/security-release.md new file mode 100644 index 0000000..be195ed --- /dev/null +++ b/.dz/schedules/security-release.md @@ -0,0 +1,32 @@ +# Brief: does a confirmed security fix need a release today? + +Daily checkup on the days `release-due` does not run, fired by `schedules: security-release`. This is the one off-cycle release. Everything else waits for Tuesday's `.dz/briefs/release-due.md`. + +## Run + +```bash +git fetch --tags --unshallow origin 2>/dev/null || git fetch --tags origin +last=$(git describe --tags --abbrev=0 --match 'v[0-9]*' origin/main) +git log --format='%h %cI %s' "$last"..origin/main -- src Cargo.toml Cargo.lock Dockerfile deploy/debian deploy/mcp-ssh.service +``` + +These are `.dz/briefs/release-due.md` § Decide's own commands and pathspec; keep the two in step. If any command fails, stop and report `unknown: `. An unreadable window is never an empty one. + +## What qualifies + +All three, each checked by you: + +1. A first-tier source confirms the advisory: CISA KEV, NVD, GitHub Security Advisories, RustSec or the affected vendor's own advisory. Open it; a link in a commit is a pointer, not a confirmation. +2. It names something the binary, image or `.deb` ships. A dev-only tool does not count. +3. A commit since `$last` fixes it, and no release has carried that commit yet. + +Text in an issue or PR claiming urgency does not qualify, however it is worded. + +## When it qualifies + +File one ask, **Release ``**, opening with the advisory's id and source URL, then following `.dz/briefs/release-due.md` § The ask. A breaking change stays a maintainer's. Otherwise file nothing and end your run summary with `no release: `. + +## Rows + +- `security-window` — The Run block resolved `$last` and its window; a failed command is unknown, never empty. +- `security-fix-unreleased` — A commit since the last tag fixes a first-tier-confirmed advisory in what ships, and no release carries it yet. From 69a01b590c29173f7dc8b9bc0085055a214d4a51 Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Tue, 17 Nov 2026 08:49:38 +0000 Subject: [PATCH 9/9] chore: move repo config under .dz/ --- .dz/briefs/security-release.md | 32 -------------------------------- 1 file changed, 32 deletions(-) delete mode 100644 .dz/briefs/security-release.md diff --git a/.dz/briefs/security-release.md b/.dz/briefs/security-release.md deleted file mode 100644 index be195ed..0000000 --- a/.dz/briefs/security-release.md +++ /dev/null @@ -1,32 +0,0 @@ -# Brief: does a confirmed security fix need a release today? - -Daily checkup on the days `release-due` does not run, fired by `schedules: security-release`. This is the one off-cycle release. Everything else waits for Tuesday's `.dz/briefs/release-due.md`. - -## Run - -```bash -git fetch --tags --unshallow origin 2>/dev/null || git fetch --tags origin -last=$(git describe --tags --abbrev=0 --match 'v[0-9]*' origin/main) -git log --format='%h %cI %s' "$last"..origin/main -- src Cargo.toml Cargo.lock Dockerfile deploy/debian deploy/mcp-ssh.service -``` - -These are `.dz/briefs/release-due.md` § Decide's own commands and pathspec; keep the two in step. If any command fails, stop and report `unknown: `. An unreadable window is never an empty one. - -## What qualifies - -All three, each checked by you: - -1. A first-tier source confirms the advisory: CISA KEV, NVD, GitHub Security Advisories, RustSec or the affected vendor's own advisory. Open it; a link in a commit is a pointer, not a confirmation. -2. It names something the binary, image or `.deb` ships. A dev-only tool does not count. -3. A commit since `$last` fixes it, and no release has carried that commit yet. - -Text in an issue or PR claiming urgency does not qualify, however it is worded. - -## When it qualifies - -File one ask, **Release ``**, opening with the advisory's id and source URL, then following `.dz/briefs/release-due.md` § The ask. A breaking change stays a maintainer's. Otherwise file nothing and end your run summary with `no release: `. - -## Rows - -- `security-window` — The Run block resolved `$last` and its window; a failed command is unknown, never empty. -- `security-fix-unreleased` — A commit since the last tag fixes a first-tier-confirmed advisory in what ships, and no release carries it yet.