- Implemented comprehensive tests for VexLensNormalizer including format detection and normalization scenarios. - Added tests for CpeParser covering CPE 2.3 and 2.2 formats, invalid inputs, and canonical key generation. - Created tests for ProductMapper to validate parsing and matching logic across different strictness levels. - Developed tests for PurlParser to ensure correct parsing of various PURL formats and validation of identifiers. - Introduced stubs for Monaco editor and worker to facilitate testing in the web application. - Updated project file for the test project to include necessary dependencies.
1017 B
1017 B
Mock Dev Release Pipeline
Purpose: provide a minimal CI artifact so deploy tasks can progress with placeholder digests until real releases land.
What it does:
- Packages
deploy/releases/2025.09-mock-dev.yamlanddeploy/downloads/manifest.jsonintoout/mock-release/mock-dev-release.tgz. - Uploads the tarball as a CI artifact (
mock-dev-release) for downstream consumers (deploy packaging, docs snapshots, local testing).
How to run locally:
mkdir -p out/mock-release
cp deploy/releases/2025.09-mock-dev.yaml out/mock-release/
cp deploy/downloads/manifest.json out/mock-release/
tar -czf out/mock-release/mock-dev-release.tgz -C out/mock-release .
CI entrypoint:
- Workflow:
.gitea/workflows/mock-dev-release.yml - Triggers: push to mock manifest/downloads files or manual
workflow_dispatch.
Notes:
- Artefacts are development-only; replace with real digests as soon as upstream releases publish.
- Keep the mock manifest and downloads JSON deterministic to avoid artifact churn.***