Niro v0.1.67

Summary

Refines report delivery in the supplied GitHub Actions workflows so the PDF opens in one click, and drops a confusing report-path line in CI. No configuration or agent-surface changes.

Changes

• GitHub workflows upload the report as its own archive: false artifact — the download is the PDF itself, no extraction — and the knowledge bundle separately as niro-knowledge. This replaces the combined niro-artifacts bundle from v0.1.66. GitLab delivery is unchanged (one browsable niro-artifacts artifact).
• The niro: report: <path> line is no longer printed on CI, where that path is on an ephemeral runner. Local runs still print it.

Security

No security-relevant behavior changed. niro-debug-logs.tar remains a separate, opt-in unsafe support artifact.

Compatibility and upgrade

• Adopt the updated examples/github-actions/ workflows: the report is its own artifact and the knowledge bundle is niro-knowledge. Update any automation that referenced the v0.1.66 niro-artifacts bundle name. GitLab examples are unchanged.
• CI no longer prints niro: report: <path>; read <config-dir>/artifacts/penetration-test-report.pdf directly. Local runs are unaffected.

Known issues

• checksums.txt covers platform archives but not niro.mcpb.
• Release artifacts have no detached signatures, provenance attestation, or SBOM.
• niro upgrade follows stable, not dev or RC; Windows users rerun the installer to change versions.