ci(ext): ship provider worker in release archives, add Windows compile gate and evidence validator tests
CI / fmt + clippy + test (Linux x86_64) (push) Waiting to run
CI / schema instance validation + consumers (push) Waiting to run
CI / runtime contract (macos-latest) (push) Waiting to run
CI / runtime contract (windows-latest) (push) Waiting to run
Linux strict security lane (G-C) / strict isolation escape matrix (push) Waiting to run
ci/woodpecker/push/main Pipeline failed

- Woodpecker test: prebuild provider helper; cross-check windows target
- Woodpecker build: release-build marqdo-cli + marqdo-provider-worker, assert helper
- GitHub release candidate: package helper as sibling and smoke assert it
- release-evidence: validate committed external-extension manifest or report UNVERIFIED
- tools/ci: unit tests for verify_extension_contracts manifest validation
- docs/ci: document the CI/CD changes
This commit is contained in:
cflmy committed 2026-11-22 01:03:52 +08:00
1 parent 2cbde54602
commit c8049d51bf
4 files changed
+132 -3

No files matched your search

+19
View File
@@ -57,6 +57,25 @@ syntax; Debian bookworm's Node 18 fails those tests.
`release-evidence` job produces a SHA-bound manifest artifact; it does not
tag or upload a release.
## RFC-EXT-0001 CI/CD additions
* The Woodpecker **test** lane builds `marqdo-provider-worker` before the
workspace tests so the provider CLI tests use the real helper, and adds a
`cargo check --workspace --all-targets --target x86_64-pc-windows-gnu`
compile gate (native Windows/macOS runtime lanes stay on the GitHub matrix).
* The Woodpecker **build** lane and the GitHub **release-candidate** lane build
`marqdo` **and** `marqdo-provider-worker` and package both as siblings; the
provider transport resolves only that sibling (no PATH fallback), so an
archive without it would silently lose provider support.
* `tools/ci/test_verify_extension_contracts.py` covers the external-extension
evidence validator in the existing `python3 -m unittest discover -s tools/ci`
step.
* The release-evidence job validates
`docs/evidence/extension/<SHA>/manifest.json` when it is committed for the
target SHA and prints `UNVERIFIED` otherwise; generating it is the mandatory
release action described in `docs/releasing.md` §7, not a substitute for
G3/G4/native lanes.
## Local reproduction
```bash