Replace the Strong/Emph/List/Quote mapping in place with the single @exec/@knowledge heading-mode model, unified payload carriers and keyword control flow. - add the authoritative RFC, ADR-0052 and a historical ADR index - rewrite spec/mapping.md and spec/expression.ebnf as the normative mapping/statement grammar; update evaluation, references, math, foreign, package-format, plugin-abi, security and schema notes - rewrite README, AGENTS, COMPATIBILITY and CHANGELOG for the breaking language change; update the architecture index/overview and active docs - mark superseded planning docs, compute RFCs, evidence and syntax-role ADRs as historical/superseded without rewriting their decisions - add migration guide, per-file inventory and dev-only audit scripts The frontend/stdlib migration is completed in the following commits; this commit contains documentation only.
62 lines
2.2 KiB
Markdown
62 lines
2.2 KiB
Markdown
# CI/CD
|
|
|
|
## Current setup
|
|
|
|
- Git remote: `https://git.cflmy.cn/cflmy/marqdo-cli.git`
|
|
- Woodpecker: `https://ci.cflmy.cn`
|
|
- Pipeline definition: [`.woodpecker.yml`](../.woodpecker.yml)
|
|
- Credentials are local-only and ignored; see
|
|
[development-credentials.md](development-credentials.md). Do not put tokens in
|
|
pipeline files or commit messages.
|
|
|
|
The default Docker pipeline runs on push and pull request:
|
|
|
|
```text
|
|
test:
|
|
rustup component add clippy rustfmt
|
|
apt install curl/ca-certificates + Node.js 22
|
|
cargo fmt --all -- --check
|
|
cargo clippy --workspace --all-targets -- -D warnings
|
|
cargo test --workspace --locked
|
|
|
|
build (depends on test):
|
|
cargo build --release --locked -p marqdo-cli
|
|
```
|
|
|
|
Node.js 22 is required because the optional foreign-kernel tests use ES-module
|
|
syntax; Debian bookworm's Node 18 fails those tests.
|
|
|
|
> **Language-syntax migration note.** `cargo test --workspace` includes
|
|
> conformance fixtures that execute `.mq.md` source. The target language is
|
|
> [RFC-LANG-0002](architecture/RFC-LANG-0002-unified-semantics.md) while the
|
|
> Rust frontend is still being migrated, so those executable-source tests are
|
|
> **expected to be red** on a correct migration branch. Do not interpret that as
|
|
> a CI-configuration regression or "fix" it by restoring the old mapper or
|
|
> regenerating goldens; see [`STATUS.md`](STATUS.md) and
|
|
> [`migration/README.md`](migration/README.md). The pipeline definition itself
|
|
> (fmt/clippy/test/build, security lane, platform gaps) is unchanged.
|
|
|
|
## What this pipeline does not cover
|
|
|
|
- **Strict security lane**: needs a disposable VM/self-hosted runner with
|
|
Bubblewrap/AppArmor namespace support. See [security-vm.md](security-vm.md).
|
|
The Docker pipeline is not an OS-isolation proof.
|
|
- **Windows/macOS native lanes**: no runners are configured.
|
|
- **Release publication/signing**: no release job is defined.
|
|
|
|
## Local reproduction
|
|
|
|
```bash
|
|
export PATH="$HOME/.cargo/bin:$PATH"
|
|
cargo fmt --all -- --check
|
|
cargo clippy --workspace --all-targets -- -D warnings
|
|
cargo test --workspace --locked
|
|
cargo build --release --locked -p marqdo-cli
|
|
```
|
|
|
|
## Local API/trigger
|
|
|
|
The ignored `.secrets/dev.env` may contain a Woodpecker API token for local
|
|
queries/triggers. The token is not needed by the pipeline itself and must never
|
|
be committed.
|