check_meta_implementation

Katz 0.355

check is a step in the sequential GitHub CI job after one workspace build.
Pull requests use ci.yml.
Main uses the same workflow through release.yml ( ci_gate ).
The job installs workspace packages once ( `pnpm install --frozen-lockfile` ), asserts `@reqlan/*` resolve under `packages/` ( assert-workspace-reqlan.mjs ), compiles crates and TypeScript, then runs crate tests, `node packages/cli/bin/cli.js check`, and JS / TS tests against that build.
Do not install `@reqlan/cli` or other `@reqlan/*` packages from npm. Platform natives in this workspace come from `packages/analytical-native/` via `packageExtensions` in pnpm-workspace.yaml, not from the registry. Do not call a global `reqlan` binary. Do not run a second install before check.
GitHub and Azure pass `--skip-gitignored-targets` because gitignored files are not in a CI checkout ( check_skip_gitignored_targets ).
Azure uses the same workspace CLI after its package build on `ext/v*` tags.
Related: check_meta_implementation check_skip_targets check_meta_implementation ci_gate

implementation

ci.yml, release.yml, azure-pipelines.yml, package.json, assert-workspace-reqlan.mjs

status

done

tests

release-ci-gate.test.ts, release-ci-gate.test.ts:release calls sequential CI before versioning, release-ci-gate.test.ts:CI is one sequential pull-request job, release-ci-gate.test.ts:one build is reused by crate tests, check, and package tests, release-ci-gate.test.ts:reference check uses workspace packages not npm, release-ci-gate.test.ts:TypeScript compile generates Langium sources first, release-ci-gate.test.ts:CI check skips gitignored targets

Interactive page: check_meta_implementation