Skip to content

ci(release): build full audit-deliverable compliance bundle (REQ-090)#322

Merged
avrabe merged 1 commit into
mainfrom
feat/req-090-release-compliance-bundle
May 24, 2026
Merged

ci(release): build full audit-deliverable compliance bundle (REQ-090)#322
avrabe merged 1 commit into
mainfrom
feat/req-090-release-compliance-bundle

Conversation

@avrabe
Copy link
Copy Markdown
Contributor

@avrabe avrabe commented May 24, 2026

Summary

REQ-090 — the GitHub Release now attaches the audit-deliverable
compliance bundle (rendered docs + coverage + matrix + validate + ReqIF

  • generic-yaml + README) instead of the ~7 MB navigation-shell HTML the
    v0.12.0 release shipped (which the v0.11.1 audit findings flagged as
    unusable).

Changes

  • `.github/actions/compliance/action.yml` — new opt-in input
    `include-data-formats` (default `false` so existing callers see
    no behaviour change). When true, the report directory gains
    `requirements.reqif`, `artifacts.yaml`, and a `README.md`
    documenting the bundle layout and DOORS/Polarion/codeBeamer import
    conventions.
  • `.github/workflows/release.yml` — `build-compliance` job
    sets `single-page: false` (the multi-page form) and
    `include-data-formats: true`. Multi-page emission is now ~50 MB
    total on the rivet corpus thanks to REQ-088's shared-assets fix
    (feat(export): extract CSS/JS to shared _assets/ + thread --filter (REQ-087, REQ-088) #319), well within a GitHub Release artifact budget. Existing
    tarball / upload / `create-release` plumbing picks the new
    contents up unchanged.

Test plan

  • Local smoke: `rivet export --format reqif --output …` and
    `--format generic-yaml --output …` produce 2.6 MB / 628 KB
    on the rivet corpus (795 artifacts).
  • YAML lint OK (both files parse).
  • CI green on this PR.
  • First real exercise = the v0.13.0 tag-push that this PR is
    paving the way for.

🤖 Generated with Claude Code

The v0.12.0 release attached a ~7 MB single-page navigation-shell HTML
bundle that auditors (per the v0.11.1 audit findings captured in
REQ-090) couldn't actually use for compliance review. The fix:

1. Compliance action gains an opt-in `include-data-formats` input
   (default false — backward compatible). When true, the report
   directory also gets:
   - `requirements.reqif` (OMG ReqIF 1.2 — importable into DOORS /
     Polarion / codeBeamer)
   - `artifacts.yaml` (generic-yaml — diff-friendly, complete)
   - `README.md` documenting the bundle layout and the importer
     conventions for ReqIF.

2. Release workflow's `build-compliance` job:
   - Sets `single-page: false` (the multi-page form, now ~50 MB on
     the rivet corpus after REQ-088's shared-assets fix landed in
     #319) — the documents/coverage/matrix/validate views auditors
     actually use.
   - Sets `include-data-formats: true` — ReqIF + generic-yaml +
     README ship inside the same tarball.

Existing tarball / upload / `create-release` plumbing picks the new
contents up unchanged.

Smoke: `rivet export --format reqif` and `--format generic-yaml`
produce 2.6 MB / 628 KB on the rivet corpus (795 artifacts) — well
within the budget.

Implements: REQ-090
@codecov
Copy link
Copy Markdown

codecov Bot commented May 24, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@avrabe avrabe merged commit 10418c4 into main May 24, 2026
19 of 38 checks passed
@avrabe avrabe deleted the feat/req-090-release-compliance-bundle branch May 24, 2026 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant