Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

chore(ci): fast Linux gate per merge, full macOS/Windows matrix pre-release

AkitaOnRails5d81d401e6d5
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 5940c538..b8e10db5 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -4,6 +4,10 @@ on:
push:
branches: [main]
pull_request:
+ types: [opened, synchronize, reopened, labeled]
+ # Manual full run (macOS legs included) — dispatch on the
+ # release-candidate SHA right before a release.
+ workflow_dispatch:
env:
CARGO_TERM_COLOR: always
@@ -40,9 +44,11 @@ jobs:
fail-fast: false
matrix:
# macOS catches stat / SELinux / case-sensitivity assumptions
- # that wouldn't show up on a Linux-only matrix. Stays in step
- # with the homelab deploy which is Linux.
- os: [ubuntu-latest, macos-latest]
+ # that wouldn't show up on a Linux-only matrix. It costs most of
+ # the wall clock, so during iteration only Linux runs; the macOS
+ # leg joins on a `full-ci` PR label or a manual dispatch, and is
+ # MANDATORY right before a release (see AGENTS.md).
+ os: ${{ (github.event_name == 'workflow_dispatch' || contains(github.event.pull_request.labels.*.name, 'full-ci')) && fromJSON('["ubuntu-latest", "macos-latest"]') || fromJSON('["ubuntu-latest"]') }}
runs-on: ${{ matrix.os }}
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
@@ -88,15 +94,11 @@ jobs:
strategy:
fail-fast: false
matrix:
- include:
- # Keep Linux on Debian bookworm so the prebuilt binary matches the
- # Docker runtime image. macOS entries mirror the release assets.
- - artifact: linux-x86_64
- runner: ubuntu-22.04
- - artifact: macos-aarch64
- runner: macos-15
- - artifact: macos-x86_64
- runner: macos-15-intel
+ # Keep Linux on Debian bookworm so the prebuilt binary matches the
+ # Docker runtime image. macOS entries mirror the release assets;
+ # they run only on `full-ci` / dispatch (mandatory pre-release),
+ # like the macOS test leg above.
+ include: ${{ (github.event_name == 'workflow_dispatch' || contains(github.event.pull_request.labels.*.name, 'full-ci')) && fromJSON('[{"artifact": "linux-x86_64", "runner": "ubuntu-22.04"}, {"artifact": "macos-aarch64", "runner": "macos-15"}, {"artifact": "macos-x86_64", "runner": "macos-15-intel"}]') || fromJSON('[{"artifact": "linux-x86_64", "runner": "ubuntu-22.04"}]') }}
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
- uses: dtolnay/rust-toolchain@4cda84d5c5c54efe2404f9d843567869ab1699d4 # stable
diff --git a/.github/workflows/windows.yml b/.github/workflows/windows.yml
index 1b2f1fac..1d65c7bc 100644
--- a/.github/workflows/windows.yml
+++ b/.github/workflows/windows.yml
@@ -29,9 +29,11 @@ name: windows
#
# If you are changing any of those areas, add the `windows` label to the
# pull request rather than finding out after the merge.
+# During feature iteration this workflow no longer runs on every push to
+# main: fast Linux CI gates each merge, and the full Windows suite runs
+# nightly, on demand, and MANDATORILY right before a release (dispatch it
+# on the release-candidate SHA and wait for green — see AGENTS.md).
on:
- push:
- branches: [main]
pull_request:
types: [opened, synchronize, reopened, labeled]
schedule:
diff --git a/AGENTS.md b/AGENTS.md
index a6824358..acc50e12 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -392,6 +392,13 @@ Additional boundary rules:
`Added`/`Changed`/`Fixed` heading, past-tense, trailing `(#NNN)`
reference) and update the relevant README/docs references in the same
commit. Internal refactors and test-only churn are exempt.
+- **CI pacing: fast per merge, full matrix before release.** Every
+ implementation merge gates on the fast Linux jobs only. The slow
+ macOS/Windows legs run on a `full-ci` PR label, nightly (windows), or
+ manual dispatch — and running them is **mandatory right before a
+ release**: dispatch `ci` (macOS legs) and `windows` on the exact
+ release-candidate SHA and wait for green before tagging. Never tag a
+ release whose SHA lacks a green full matrix.
- **No version bumps or release tags without explicit user approval.**
Do not bump crate/package versions automatically.
- **PR evaluation:** report pros, cons, and recommended fix, then ask for
diff --git a/docs/ROADMAP-2.0.md b/docs/ROADMAP-2.0.md
index 9f6a545c..0bea7012 100644
--- a/docs/ROADMAP-2.0.md
+++ b/docs/ROADMAP-2.0.md
@@ -176,8 +176,10 @@ for. Most speculative, therefore last - and shaped by whatever items
```
Each lands on main individually gated (fmt, clippy -D warnings, full
-tests, changelog guards, harness numbers where retrieval is touched).
-2.0 is cut when:
+tests, changelog guards, harness numbers where retrieval is touched) —
+**fast Linux CI only per item**; the slow macOS/Windows matrix runs
+once, mandatorily, on the release-candidate SHA before the cut (see
+AGENTS.md "CI pacing"). 2.0 is cut when:
- all six items (or an explicitly-decided subset - item 6 may justifiably
drop) are merged with docs;
@@ -185,7 +187,11 @@ tests, changelog guards, harness numbers where retrieval is touched).
exercised against a copy of a real 1.x data dir, **including a full
restore drill from the pre-migration backup archive**;
- README/ARCHITECTURE reflect 2.0 reality;
-- the eval numbers are re-run and published for the final tree.
+- the eval numbers are re-run and published for the final tree;
+- the full macOS/Windows CI matrix is green on the release-candidate
+ SHA (dispatched, not assumed), and **the user has reviewed the summary
+ of everything done and explicitly approved the release** — 2.0 is
+ never cut automatically.
Deploy/live-test follows the same v1.39 pipeline: exact-main gates,
hosted CI, `compose pull` (never `bin/deploy`), health + status + a