From 89ebaa470c8c60ec12b98ad5d215819d5311b9b7 Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 20:58:48 +0000 Subject: [PATCH 01/11] chore: move repo config under .dz/ --- .dz/maintainer/maintainer.yml | 24 +++++++++++++++++++----- 1 file changed, 19 insertions(+), 5 deletions(-) diff --git a/.dz/maintainer/maintainer.yml b/.dz/maintainer/maintainer.yml index 1cfed09..ae53964 100644 --- a/.dz/maintainer/maintainer.yml +++ b/.dz/maintainer/maintainer.yml @@ -104,21 +104,35 @@ schedules: - name: release-due days: [thu] 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, tue, wed, fri, sat, sun] hours_utc: [1] - brief_file: .dz/briefs/security-release.md + brief_file: .dz/schedules/security-release.md - name: health days: [mon, tue, wed, thu, fri, sat, sun] hours_utc: [7] - brief_file: .dz/briefs/health.md + brief_file: .dz/schedules/health.md - name: improve days: [mon] hours_utc: [8] - brief_file: .dz/briefs/improve.md + brief_file: .dz/schedules/improve.md - name: compat days: [wed] hours_utc: [8] - brief_file: .dz/briefs/compat.md + brief_file: .dz/schedules/compat.md + +# Added by the developerz.ai maintainer agent: blocks from the current template this file did not have. Each states the value already in effect; edit it like any other key. + +# branches: on at 60 because this file exists. A branch with no new commit +# this long is tagged archive// at its last commit, then deleted. +# false keeps every branch. See /docs/maintainer-yml. +branches: + close_inactive_after_days: 60 + +# scout: the platform's daily survey of this repo files only what is already BROKEN +# (red CI, failing tests, a security advisory, a broken build or link) — never an +# improvement idea. `full` lets it file ideas too; `off` stops the survey. +scout: + survey: broken_only From 5aa27ee27ad21f09a4dae897b445968be5fce990 Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 20:58:49 +0000 Subject: [PATCH 02/11] chore: move repo config under .dz/ --- .dz/schedules/compat.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 .dz/schedules/compat.md diff --git a/.dz/schedules/compat.md b/.dz/schedules/compat.md new file mode 100644 index 0000000..a3e774d --- /dev/null +++ b/.dz/schedules/compat.md @@ -0,0 +1,21 @@ +# Brief: are we still drop-in? + +Weekly checkup, fired by `schedules: compat`. Drop-in is pillar 1; upstream moves every week. + +1. For each gem in `apps/fast-rspec/fast_rspec.gemspec` and `docs/target/*.md`: `gem list --remote --exact` vs the version the target doc is dated against. +2. A new upstream minor/major → read its CHANGELOG for changes to the surface in the target doc. +3. Surface changed → update `docs/target/.md` first, then open one issue per change (`compat` label) with the upstream link and the doc diff. +4. Oracles (`bin/rake test:oracles`) still pinned to a SHA older than the latest release → one PR bumping the pin; it merges only on green. +5. Run `bin/rake test:oracles`. If verification cannot run — a missing launcher, an existing launcher with an unimplemented oracle task, or another execution blocker — report an explicit **blocked/unavailable** finding with the command, reason (including exact error output when available), and scope left unverified. Launcher existence alone does not establish availability. + +Report upstream release/version and pin observations separately from oracle execution outcomes. Describe an oracle as **passed** only after a completed successful run, identifying the scope it verified. Failed or incomplete runs are not passes; report their errors and unverified scope. + +No change upstream → do nothing only when supported by completed upstream checks and no blocked/unavailable oracle finding remains to report. Unavailable verification is never evidence of no upstream change and never permits an overall “no change upstream” conclusion; report the blocker even if independent release/version and pin observations show no changes. + +## Rows + +- `upstream-version-check` — For each gem in `apps/fast-rspec/fast_rspec.gemspec` and `docs/target/*.md`: `gem list --remote --exact` vs the version the target doc is dated against. +- `upstream-changelog-review` — A new upstream minor/major → read its CHANGELOG for changes to the surface in the target doc. +- `target-doc-update-and-issue` — Surface changed → update `docs/target/.md` first, then open one issue per change (`compat` label) with the upstream link and the doc diff. +- `oracle-pin-bump` — Oracles (`bin/rake test:oracles`) still pinned to a SHA older than the latest release → one PR bumping the pin; it merges only on green. +- `oracle-suite-run` — Run `bin/rake test:oracles`. If verification cannot run — a missing launcher, an existing launcher with an unimplemented oracle task, or another execution blocker — report an explicit **blocked/unavailable** finding with the command, reason (including exact error output when available), and scope left unverified. Launcher existence alone does not establish availability. From d955f76b37a1d53991aca33d6e605d5db3c03e9a Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 20:58:51 +0000 Subject: [PATCH 03/11] chore: move repo config under .dz/ --- .dz/briefs/compat.md | 21 --------------------- 1 file changed, 21 deletions(-) delete mode 100644 .dz/briefs/compat.md diff --git a/.dz/briefs/compat.md b/.dz/briefs/compat.md deleted file mode 100644 index a3e774d..0000000 --- a/.dz/briefs/compat.md +++ /dev/null @@ -1,21 +0,0 @@ -# Brief: are we still drop-in? - -Weekly checkup, fired by `schedules: compat`. Drop-in is pillar 1; upstream moves every week. - -1. For each gem in `apps/fast-rspec/fast_rspec.gemspec` and `docs/target/*.md`: `gem list --remote --exact` vs the version the target doc is dated against. -2. A new upstream minor/major → read its CHANGELOG for changes to the surface in the target doc. -3. Surface changed → update `docs/target/.md` first, then open one issue per change (`compat` label) with the upstream link and the doc diff. -4. Oracles (`bin/rake test:oracles`) still pinned to a SHA older than the latest release → one PR bumping the pin; it merges only on green. -5. Run `bin/rake test:oracles`. If verification cannot run — a missing launcher, an existing launcher with an unimplemented oracle task, or another execution blocker — report an explicit **blocked/unavailable** finding with the command, reason (including exact error output when available), and scope left unverified. Launcher existence alone does not establish availability. - -Report upstream release/version and pin observations separately from oracle execution outcomes. Describe an oracle as **passed** only after a completed successful run, identifying the scope it verified. Failed or incomplete runs are not passes; report their errors and unverified scope. - -No change upstream → do nothing only when supported by completed upstream checks and no blocked/unavailable oracle finding remains to report. Unavailable verification is never evidence of no upstream change and never permits an overall “no change upstream” conclusion; report the blocker even if independent release/version and pin observations show no changes. - -## Rows - -- `upstream-version-check` — For each gem in `apps/fast-rspec/fast_rspec.gemspec` and `docs/target/*.md`: `gem list --remote --exact` vs the version the target doc is dated against. -- `upstream-changelog-review` — A new upstream minor/major → read its CHANGELOG for changes to the surface in the target doc. -- `target-doc-update-and-issue` — Surface changed → update `docs/target/.md` first, then open one issue per change (`compat` label) with the upstream link and the doc diff. -- `oracle-pin-bump` — Oracles (`bin/rake test:oracles`) still pinned to a SHA older than the latest release → one PR bumping the pin; it merges only on green. -- `oracle-suite-run` — Run `bin/rake test:oracles`. If verification cannot run — a missing launcher, an existing launcher with an unimplemented oracle task, or another execution blocker — report an explicit **blocked/unavailable** finding with the command, reason (including exact error output when available), and scope left unverified. Launcher existence alone does not establish availability. From ada4ec45f3ae4f60b5b757ae05617bd0d45fdd05 Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 20:58:53 +0000 Subject: [PATCH 04/11] chore: move repo config under .dz/ --- .dz/schedules/health.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 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..ca4e86d --- /dev/null +++ b/.dz/schedules/health.md @@ -0,0 +1,24 @@ +# Brief: is the project healthy? + +Daily checkup, fired by `schedules: health` in `.dz/maintainer/maintainer.yml`. fast_rspec is +maintained so that nobody has to watch it. This covers 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` | `success` | +| the last release published | `gh run list --workflow release.yml --limit 1 --json conclusion,displayTitle` | `success` (or no run yet) | +| RubyGems serves `FastRspec::VERSION` | `gem list fast_rspec --remote --exact` vs `apps/fast-rspec/lib/fast_rspec/version.rb` | equal, or a release run is in flight | +| Dependabot is not stuck | `gh pr list --app dependabot --json number,createdAt` | none older than 7 days | +| canary ran | `gh run list --workflow canary.yml --limit 1 --json conclusion,createdAt` | a run in the last 35 days (its failures are `improve`'s job) | + +## Rows + +- `main-green` — `main` is green +- `release-published` — the last release published +- `rubygems-version-served` — RubyGems serves `FastRspec::VERSION` +- `dependabot-not-stuck` — Dependabot is not stuck +- `canary-ran` — canary ran + +For each unhealthy signal, file one issue unless an open issue already names it. Title names the +signal (`main is red at `); body carries the command, its output and the run URL. A red `main` +comes first. Never delete a tag, re-run a publish or `gem push` from here. From b0c3d78975a8d53ebf791878c6ba2b5e4b2f770d Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 20:58:54 +0000 Subject: [PATCH 05/11] chore: move repo config under .dz/ --- .dz/briefs/health.md | 24 ------------------------ 1 file changed, 24 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 ca4e86d..0000000 --- a/.dz/briefs/health.md +++ /dev/null @@ -1,24 +0,0 @@ -# Brief: is the project healthy? - -Daily checkup, fired by `schedules: health` in `.dz/maintainer/maintainer.yml`. fast_rspec is -maintained so that nobody has to watch it. This covers 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` | `success` | -| the last release published | `gh run list --workflow release.yml --limit 1 --json conclusion,displayTitle` | `success` (or no run yet) | -| RubyGems serves `FastRspec::VERSION` | `gem list fast_rspec --remote --exact` vs `apps/fast-rspec/lib/fast_rspec/version.rb` | equal, or a release run is in flight | -| Dependabot is not stuck | `gh pr list --app dependabot --json number,createdAt` | none older than 7 days | -| canary ran | `gh run list --workflow canary.yml --limit 1 --json conclusion,createdAt` | a run in the last 35 days (its failures are `improve`'s job) | - -## Rows - -- `main-green` — `main` is green -- `release-published` — the last release published -- `rubygems-version-served` — RubyGems serves `FastRspec::VERSION` -- `dependabot-not-stuck` — Dependabot is not stuck -- `canary-ran` — canary ran - -For each unhealthy signal, file one issue unless an open issue already names it. Title names the -signal (`main is red at `); body carries the command, its output and the run URL. A red `main` -comes first. Never delete a tag, re-run a publish or `gem push` from here. From 9864ecda2a79b8fbb65c2c470317e55daa32ba98 Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 20:58:56 +0000 Subject: [PATCH 06/11] chore: move repo config under .dz/ --- .dz/schedules/improve.md | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 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..ac2e51a --- /dev/null +++ b/.dz/schedules/improve.md @@ -0,0 +1,38 @@ +# Brief: monthly improvement + +Fired every Monday by `schedules: improve`. **Act only on the first Monday of the month (UTC day 1-7); +otherwise stop.** fast_rspec is maintained by agents only. Once a month, leave it measurably faster +and one step ahead of the next Ruby, Rails and RSpec/Minitest release. Read `AGENTS.md` first. + +## 1. Canary first +`gh run list --workflow canary.yml --limit 1 --json conclusion,url,createdAt` (Ruby head, Rails edge, +rspec/minitest main). Fix ours; file upstream-linked issues for theirs, never shims. No run in 7 days → +`gh workflow run canary.yml` and read it before step 3. + +## 2. At most three improvements, in this order +1. Anything the canary found. +2. Compat: open `compat`-labelled issues; failing oracles. +3. Speed: run `bin/rake bench` on `main`; pick a trick from `docs/idea/08-performance.md` + (🔬 → ✅). If the bench launcher or rake task is unavailable (missing command, abort like + Rakefile's `abort 'bench: not implemented yet'`, or a non-zero exit), record the speed step as an + explicit BLOCKED result in the run report: the exact command and its failure output. Never record + it as passed and never skip it silently. Only real before/after numbers, measured by a working + benchmark and recorded in `docs/benchmarks.md`, count as performance evidence; a blocked run, an + estimate or a fabricated number never does. +4. Correctness: open `bug` issues; flaky-under-parallel reports first. +5. Docs drift: `README.md`, `AGENTS.md`, `llms.txt`, `docs/target/*` still match the code and upstream. +6. Simplification: dead code, slow or flaky tests. + +## 3. Ship +One PR per improvement, with evidence (canary log, bench table, failing test). User-visible → +CHANGELOG `## [Unreleased]`. Never bump the version here. Nothing worth changing → do nothing. + + +## Rows + +- `canary` — Canary freshness, results and findings: read the latest run; if none in 7 days, trigger it and read it before step 3. Fix ours; file upstream-linked issues for theirs, never shims. +- `compat` — Open `compat`-labelled issues and failing oracles. +- `speed` — Run `bin/rake bench` on `main`; pick a trick from `docs/idea/08-performance.md` (🔬 → ✅). If the launcher or task is unavailable or exits non-zero, report an explicit BLOCKED result with the exact command and failure output, never a pass or silent skip. Only real before/after numbers from a working benchmark, recorded in `docs/benchmarks.md`, count as performance evidence; blocked runs, estimates and fabricated numbers do not. +- `correctness` — Open `bug` issues, with flaky-under-parallel reports first. +- `docs-drift` — Check that `README.md`, `AGENTS.md`, `llms.txt` and `docs/target/*` still match the code and upstream. +- `simplification` — Dead code and slow or flaky tests. From 2c94a0b4ca459ec263e94702782179b31fee59a5 Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 20:58:57 +0000 Subject: [PATCH 07/11] chore: move repo config under .dz/ --- .dz/briefs/improve.md | 38 -------------------------------------- 1 file changed, 38 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 ac2e51a..0000000 --- a/.dz/briefs/improve.md +++ /dev/null @@ -1,38 +0,0 @@ -# Brief: monthly improvement - -Fired every Monday by `schedules: improve`. **Act only on the first Monday of the month (UTC day 1-7); -otherwise stop.** fast_rspec is maintained by agents only. Once a month, leave it measurably faster -and one step ahead of the next Ruby, Rails and RSpec/Minitest release. Read `AGENTS.md` first. - -## 1. Canary first -`gh run list --workflow canary.yml --limit 1 --json conclusion,url,createdAt` (Ruby head, Rails edge, -rspec/minitest main). Fix ours; file upstream-linked issues for theirs, never shims. No run in 7 days → -`gh workflow run canary.yml` and read it before step 3. - -## 2. At most three improvements, in this order -1. Anything the canary found. -2. Compat: open `compat`-labelled issues; failing oracles. -3. Speed: run `bin/rake bench` on `main`; pick a trick from `docs/idea/08-performance.md` - (🔬 → ✅). If the bench launcher or rake task is unavailable (missing command, abort like - Rakefile's `abort 'bench: not implemented yet'`, or a non-zero exit), record the speed step as an - explicit BLOCKED result in the run report: the exact command and its failure output. Never record - it as passed and never skip it silently. Only real before/after numbers, measured by a working - benchmark and recorded in `docs/benchmarks.md`, count as performance evidence; a blocked run, an - estimate or a fabricated number never does. -4. Correctness: open `bug` issues; flaky-under-parallel reports first. -5. Docs drift: `README.md`, `AGENTS.md`, `llms.txt`, `docs/target/*` still match the code and upstream. -6. Simplification: dead code, slow or flaky tests. - -## 3. Ship -One PR per improvement, with evidence (canary log, bench table, failing test). User-visible → -CHANGELOG `## [Unreleased]`. Never bump the version here. Nothing worth changing → do nothing. - - -## Rows - -- `canary` — Canary freshness, results and findings: read the latest run; if none in 7 days, trigger it and read it before step 3. Fix ours; file upstream-linked issues for theirs, never shims. -- `compat` — Open `compat`-labelled issues and failing oracles. -- `speed` — Run `bin/rake bench` on `main`; pick a trick from `docs/idea/08-performance.md` (🔬 → ✅). If the launcher or task is unavailable or exits non-zero, report an explicit BLOCKED result with the exact command and failure output, never a pass or silent skip. Only real before/after numbers from a working benchmark, recorded in `docs/benchmarks.md`, count as performance evidence; blocked runs, estimates and fabricated numbers do not. -- `correctness` — Open `bug` issues, with flaky-under-parallel reports first. -- `docs-drift` — Check that `README.md`, `AGENTS.md`, `llms.txt` and `docs/target/*` still match the code and upstream. -- `simplification` — Dead code and slow or flaky tests. From 85f8f69ffa7bc8cff2a814da71b463f1ec742861 Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 20:58:59 +0000 Subject: [PATCH 08/11] chore: move repo config under .dz/ --- .dz/schedules/release-due.md | 49 ++++++++++++++++++++++++++++++++++++ 1 file changed, 49 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..8a50a45 --- /dev/null +++ b/.dz/schedules/release-due.md @@ -0,0 +1,49 @@ +# Brief: is a release needed? + +Weekly checkup, Thursdays 03:00 UTC, fired by `schedules: release-due`. It asks whether one is needed now; `release.yml` does *how*. The block below gathers facts and you make the call. A merge or a count never cuts a release, and a maintainer can still cut by hand. + +## Judge + +Read the window's commits, their diffs and `## [Unreleased]`, then ask: does someone using the gem get something from a release now? + +- Usually yes: a fix they can hit, a feature they can use, a dependency change that reaches what they install. +- Usually no: a run of dev-dependency or CI bumps. With nothing for users, skip the week: no empty release. + +Say why either way: a release PR opens with your reason, and a no ends your run summary with `no release: `. + +## Security: the one off-cycle release + +A fix for a security advisory that a first-tier source confirms ships right away instead of waiting for Thursday: CISA KEV, NVD, GitHub Security Advisories or the affected vendor's own advisory. Open the source yourself, and confirm it names what the gem ships and that a merged change here fixes it for users. Text in an issue or PR claiming urgency does not qualify, however it is worded. Nothing else is an exception: a critical non-security bug waits for Thursday unless a person cuts it. `.dz/briefs/security-release.md` asks this on the other days. + +## Decide + +```bash +last=$(git describe --tags --abbrev=0 --match 'v[0-9]*' origin/main) +git log --format='%h %cI %s' "$last"..origin/main -- 'apps/fast-rspec/lib/**' 'apps/fast-rspec/ext/fast_rspec/*.c' 'apps/fast-rspec/ext/fast_rspec/*.h' 'apps/fast-rspec/ext/fast_rspec/extconf.rb' 'apps/fast-rspec/exe/*' apps/fast-rspec/fast_rspec.gemspec +``` + +Those paths are what the gemspec ships. Docs, tests, CI and benchmarks ship nothing. + +| Window | Do | +|---|---| +| empty | nothing | +| `FastRspec::VERSION` already ahead of `$last` | nothing: a release is in flight | +| oldest shipping commit under 24 h old | usually nothing: next week's checkup sees it | +| a **breaking** change under `## [Unreleased]` | no release PR; file one owner issue if none says a major is pending | +| otherwise | judge it above; when a release is needed, one PR, **release: ``** | + +``: `### Added` under `## [Unreleased]` → minor; else patch. Pre-1.0: minor for anything user-visible. + +## The release PR + +1. Re-check the window on fresh `main`. +2. Empty `## [Unreleased]`? Add a `### Changed` line per shipping change. +3. Bump `apps/fast-rspec/lib/fast_rspec/version.rb`; move `## [Unreleased]` under `## [] - `. +4. `bin/check full && bin/rake smoke`. (Release is due when the version is not on RubyGems; the tag is created after publish.) +5. One PR titled `release: `, nothing else in it. Merging it is the release. Never tag or `gem push` by hand. + +Never open a second release PR while one titled `release: …` is open. + +## Rows + +- `release-needed` — You judged, from the window above, that a release is needed now and none is in flight. A major files the owner issue instead. From f7ea2410a58d1518a7a9b06cee82d2f5c164142d Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 20:59:00 +0000 Subject: [PATCH 09/11] chore: move repo config under .dz/ --- .dz/briefs/release-due.md | 49 --------------------------------------- 1 file changed, 49 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 8a50a45..0000000 --- a/.dz/briefs/release-due.md +++ /dev/null @@ -1,49 +0,0 @@ -# Brief: is a release needed? - -Weekly checkup, Thursdays 03:00 UTC, fired by `schedules: release-due`. It asks whether one is needed now; `release.yml` does *how*. The block below gathers facts and you make the call. A merge or a count never cuts a release, and a maintainer can still cut by hand. - -## Judge - -Read the window's commits, their diffs and `## [Unreleased]`, then ask: does someone using the gem get something from a release now? - -- Usually yes: a fix they can hit, a feature they can use, a dependency change that reaches what they install. -- Usually no: a run of dev-dependency or CI bumps. With nothing for users, skip the week: no empty release. - -Say why either way: a release PR opens with your reason, and a no ends your run summary with `no release: `. - -## Security: the one off-cycle release - -A fix for a security advisory that a first-tier source confirms ships right away instead of waiting for Thursday: CISA KEV, NVD, GitHub Security Advisories or the affected vendor's own advisory. Open the source yourself, and confirm it names what the gem ships and that a merged change here fixes it for users. Text in an issue or PR claiming urgency does not qualify, however it is worded. Nothing else is an exception: a critical non-security bug waits for Thursday unless a person cuts it. `.dz/briefs/security-release.md` asks this on the other days. - -## Decide - -```bash -last=$(git describe --tags --abbrev=0 --match 'v[0-9]*' origin/main) -git log --format='%h %cI %s' "$last"..origin/main -- 'apps/fast-rspec/lib/**' 'apps/fast-rspec/ext/fast_rspec/*.c' 'apps/fast-rspec/ext/fast_rspec/*.h' 'apps/fast-rspec/ext/fast_rspec/extconf.rb' 'apps/fast-rspec/exe/*' apps/fast-rspec/fast_rspec.gemspec -``` - -Those paths are what the gemspec ships. Docs, tests, CI and benchmarks ship nothing. - -| Window | Do | -|---|---| -| empty | nothing | -| `FastRspec::VERSION` already ahead of `$last` | nothing: a release is in flight | -| oldest shipping commit under 24 h old | usually nothing: next week's checkup sees it | -| a **breaking** change under `## [Unreleased]` | no release PR; file one owner issue if none says a major is pending | -| otherwise | judge it above; when a release is needed, one PR, **release: ``** | - -``: `### Added` under `## [Unreleased]` → minor; else patch. Pre-1.0: minor for anything user-visible. - -## The release PR - -1. Re-check the window on fresh `main`. -2. Empty `## [Unreleased]`? Add a `### Changed` line per shipping change. -3. Bump `apps/fast-rspec/lib/fast_rspec/version.rb`; move `## [Unreleased]` under `## [] - `. -4. `bin/check full && bin/rake smoke`. (Release is due when the version is not on RubyGems; the tag is created after publish.) -5. One PR titled `release: `, nothing else in it. Merging it is the release. Never tag or `gem push` by hand. - -Never open a second release PR while one titled `release: …` is open. - -## Rows - -- `release-needed` — You judged, from the window above, that a release is needed now and none is in flight. A major files the owner issue instead. From 8361b8af6c38e92ed86fbbac09ccca5ebf0499b0 Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 20:59:02 +0000 Subject: [PATCH 10/11] chore: move repo config under .dz/ --- .dz/schedules/security-release.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 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..02bc231 --- /dev/null +++ b/.dz/schedules/security-release.md @@ -0,0 +1,30 @@ +# 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 Thursday's `.dz/briefs/release-due.md`, and a person can still cut by hand. + +## Run + +```bash +last=$(git describe --tags --abbrev=0 --match 'v[0-9]*' origin/main) +git log --format='%h %cI %s' "$last"..origin/main -- 'lib/**' 'ext/fast_rspec/*.c' 'ext/fast_rspec/*.h' 'ext/fast_rspec/extconf.rb' 'exe/*' fast_rspec.gemspec +``` + +Those paths are what the gemspec ships; look there for a commit that fixes a security advisory. + +## What qualifies + +All three, each checked by you: + +1. A first-tier source confirms the advisory: CISA KEV, NVD, GitHub Security Advisories 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 gem ships to users. 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. A severe bug with no such advisory does not qualify: it waits for Thursday unless a person cuts it. + +## When it qualifies + +Open one PR, **release: ``**, with the advisory's id and source URL first in its body, following `.dz/briefs/release-due.md` § The release PR. A breaking change stays the owner's. Otherwise file nothing and end your run summary with `no release: `. + +## Rows + +- `security-fix-unreleased` — A commit since the last tag fixes an advisory a first-tier source confirms, naming something the gem ships, and no release carries it yet. From 21540b97e06870790f8e603e51fe442eaf12a3ed Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 20:59:03 +0000 Subject: [PATCH 11/11] chore: move repo config under .dz/ --- .dz/briefs/security-release.md | 30 ------------------------------ 1 file changed, 30 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 02bc231..0000000 --- a/.dz/briefs/security-release.md +++ /dev/null @@ -1,30 +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 Thursday's `.dz/briefs/release-due.md`, and a person can still cut by hand. - -## Run - -```bash -last=$(git describe --tags --abbrev=0 --match 'v[0-9]*' origin/main) -git log --format='%h %cI %s' "$last"..origin/main -- 'lib/**' 'ext/fast_rspec/*.c' 'ext/fast_rspec/*.h' 'ext/fast_rspec/extconf.rb' 'exe/*' fast_rspec.gemspec -``` - -Those paths are what the gemspec ships; look there for a commit that fixes a security advisory. - -## What qualifies - -All three, each checked by you: - -1. A first-tier source confirms the advisory: CISA KEV, NVD, GitHub Security Advisories 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 gem ships to users. 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. A severe bug with no such advisory does not qualify: it waits for Thursday unless a person cuts it. - -## When it qualifies - -Open one PR, **release: ``**, with the advisory's id and source URL first in its body, following `.dz/briefs/release-due.md` § The release PR. A breaking change stays the owner's. Otherwise file nothing and end your run summary with `no release: `. - -## Rows - -- `security-fix-unreleased` — A commit since the last tag fixes an advisory a first-tier source confirms, naming something the gem ships, and no release carries it yet.