Skip to content

v0.3.28

Choose a tag to compare

@github-actions github-actions released this 07 Nov 03:25
· 19 commits to main since this release
Immutable release. Only release title and notes can be modified.
cc3b384
  • fix a real, residual gap in v0.3.27's own REQ-017 fix: only 1 of the 5 credential-cleanup sites in provision-windows-labview-vm.yml (create-vm) had actually been moved trap-before-write despite the v0.3.27 CHANGELOG/compliance stamp claiming all 5 were fixed; the other 4 (Attach Installer Media And Restart, install-vipm, install-labview, register-runner) still wrote credential file(s) before installing the trap -- fixed all 5, re-verified with an automated step-boundary scanner (not manual re-reading, since manual reading had already missed this once) plus a live bash simulation of the exact failure scenario
  • fix .github/scripts/validate-vm-provisioning-dispatch.py: restored this genuinely generic dispatch-contract validator to this engine, which was missing from the original ProjectBuddy extraction (confirmed by its real, unmodified presence in the VITechnologies/SandboxSBOMReporting consumer repo) -- provision-ubuntu-vm.yml's "Validate Dispatch Contract" step previously failed unconditionally on every phase for every dispatch because this script did not exist here; local simulation confirms the step now passes for representative validate-phase inputs. vm/ubuntu-labview/build-vip-package.sh remains deliberately absent (confirmed as an intentional, disclosed, consumer-vendored exception, not a dropped file like the validator was) -- added an explicit doc comment to the package-build phase clarifying this (#62 updated with the corrected root cause)
  • fix .github/workflows/release.yml: it interpolated ${{ steps.changelog.outputs.notes }}/${{ inputs.version }} directly into run: script bodies -- an expression-injection anti-pattern under a contents: write token, reproduced as a real bash syntax error using v0.3.27's own CHANGELOG entry (18 embedded double quotes). Rewrote to pass all inputs via env: and write release notes to a file for gh release create --notes-file, verified end-to-end against the real v0.3.27 entry
  • fix vm-fleet-status.yml: its generate-matrix job called jq directly on runner-inventory.json, which is never committed in this public engine repo by design -- every scheduled run failed with a jq: error: Could not open file (confirmed via real run logs). Now emits an empty matrix and a clear ::notice:: instead of failing when the file is absent
  • fix README.md: (1) the "every VM identity value... no built-in default" claim (script-level build-virtualbox.ps1/.sh parameters) didn't account for Iso/GuestUser/WinRmHostPort genuinely having generic, non-identity defaults; (2) vm-fleet-status.yml was incorrectly grouped with the two provisioning workflows as taking "every real identity value" as an explicit input, when it actually takes zero workflow_dispatch inputs; (3) the "zero pre-committed project configs" claim is contradicted by real, tracked violations (#68) -- added an explicit caveat; (4) the "never vendored/copied script files" claim omitted the already-accepted #48 exception for workflow_dispatch-only workflows, which a consumer genuinely vendors its own copy of
  • fix Run-Pipeline.ps1: its own Linux-guard error message said "On Linux, use Run-Pipeline.sh", actively pointing users at a script this same session already established is not a SBOM pipeline at all
  • fix docker/linux-sbom/linux_sbom_pipeline.py: the Grype gate stage recorded gate="passed" even when GRYPE_FAIL_ON=none (i.e. not actually gated), diverging from the Windows container pipeline's more honest "not-gated" status for the same situation -- aligned Linux's reporting to match
  • fix .github/workflows/ci-assurance.yml: pinned previously-unversioned pip/pytest/pytest-cov/pyyaml installs to the exact versions a real recent CI run proved against, and fixed a dangling docs/requirements/srs.md reference (that path only exists ephemerally during an active standards-assurance-scan.yml run, not as a permanently committed file) in both this workflow and scripts/tests/test_convert_vipb_json.py's docstring, pointing both at the wiki's real, permanent SRS location instead
  • fix docs/cm/cm-plan.md, CONTRIBUTING.md, and wiki REQ-010: the merge-back-to-develop no-op exception added in v0.3.27 was only documented in docs/release/release-procedure.md -- propagated the same caveat to the other 3 places that described merge-back as unconditional
  • fix docs/cm/cm-plan.md's "every release" audit-trail claim: didn't account for pre-GitFlow releases (before v0.3.9), which were tagged under the prior trunk-based model per ADR-0001 and have no release/* branch ancestry
  • fix docs/release/release-procedure.md: (1) the GitFlow Branch Rules summary's hotfix merge-back bullet read as an either/or between develop and an active release branch, when the detailed Hotfix Flow steps are additive (always develop, plus an active release branch if one exists); (2) the Feature Flow only documented the older sync-from-fork-<date> branch-naming pattern, omitting the sync-upstream-develop-*/sync-upstream-main-vX.Y.Z patterns actually used in recent practice, and never explained the post-release fork-sync step that is why develop/main are usually already content-identical by the merge-back step
  • fix the wiki Architecture Packet: (1) the Deployment View's Ubuntu-lifecycle caveat only said the package-ready snapshot was unreachable, when in fact every phase was unreachable (same root cause, now partly fixed above); (2) still called VIPM activation "LabVIEW-gated" after v0.3.27's own REQ-032 correction established it isn't; (3) the Component View's internal/Pipeline.Stages.ps1 row claimed 8 ordered stage functions including a preceding "policy gate" stage, when there are 6, and the policy-gate check is a helper called at the end of Publish-DependencyTrack, not a separate preceding stage; (4) the package-vagrant-box.py/receipt-scripts row claimed a package-ready receipt verifier exists; it doesn't; (5) the vipm-exit-codes.json/pipeline-config.schema.json row claimed both the native and both containerized pipelines validate against the schema, but the Linux container pipeline does its own separate, narrower inline validation instead; (6) the build-virtualbox.ps1/.sh rows repeated the same no-default overclaim fixed in README above; (7) added 6 previously-undocumented components to the Component View (batch-provision.sh, Register-WindowsRunner.ps1, Register-WslRunnerKeepAlive.ps1, Test-SbomArtifact.ps1, scripts/Test-ToolchainPresence.ps1+toolchain-smoke-test.yml, scripts/Convert-VipbJson.py)
  • fix docs/vm-provisioning/procedure.md: resolved a dangling "tracked as a follow-up gap" reference for the hostname-collision risk (no issue actually tracked it) by filing #69 and linking it; added a reachability caveat to the Ubuntu lifecycle phase list matching the Architecture Packet fix above
  • file #68: a broader, previously-untracked REQ-001 violation -- hardcoded project-specific identifiers in Register-WslRunnerKeepAlive.ps1, vm/ubuntu-labview/base-bootstrap.sh and 5 other scripts sharing its /SandboxSBOMReporting/SshHostEd25519Fingerprint guest-property path, and Run-WindowsSbom.ps1/Run-LinuxSbom.ps1's own .DESCRIPTION text -- beyond what #62 already tracked
  • file #69: batch-provision.sh gives every VM in a batch the same in-guest hostname/full name (a real collision risk, not safely auto-fixable given Windows's 15-character NetBIOS hostname limit)
  • file #70: ALLOW_PACKAGE_DRIFT's default is opposite between the native pipeline (off) and both containerized pipelines (on); REQ-008/REQ-009's "validated via real CI dispatch instead" justification doesn't hold for toolchain-smoke-test.yml (never actually called in this repo) or Test-SbomArtifact.ps1 (pure offline code, never fixtured); compliance-scan "Known tradeoffs" correspondence overclaims its own evidence strength for physical-host/PDF-corpus claims
  • all findings from this round's --mode semantic-audit pass (same 3-model delegation, explicitly asked to verify whether v0.3.27's fixes held up and hunt for anything neither prior round caught): 2 real regressions found and fixed (the REQ-017 trap-ordering miss above, and this round's own corrected root-cause for #62); #62/#63 updated with corrected evidence