Repository navigation
v0.3.28
·
19 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
- fix a real, residual gap in
v0.3.27's own REQ-017 fix: only 1 of the 5 credential-cleanup sites inprovision-windows-labview-vm.yml(create-vm) had actually been moved trap-before-write despite thev0.3.27CHANGELOG/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 theVITechnologies/SandboxSBOMReportingconsumer 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 representativevalidate-phase inputs.vm/ubuntu-labview/build-vip-package.shremains deliberately absent (confirmed as an intentional, disclosed, consumer-vendored exception, not a dropped file like the validator was) -- added an explicit doc comment to thepackage-buildphase clarifying this (#62updated with the corrected root cause) - fix
.github/workflows/release.yml: it interpolated${{ steps.changelog.outputs.notes }}/${{ inputs.version }}directly intorun:script bodies -- an expression-injection anti-pattern under acontents: writetoken, reproduced as a real bash syntax error usingv0.3.27's own CHANGELOG entry (18 embedded double quotes). Rewrote to pass all inputs viaenv:and write release notes to a file forgh release create --notes-file, verified end-to-end against the realv0.3.27entry - fix
vm-fleet-status.yml: itsgenerate-matrixjob calledjqdirectly onrunner-inventory.json, which is never committed in this public engine repo by design -- every scheduled run failed with ajq: 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-levelbuild-virtualbox.ps1/.shparameters) didn't account forIso/GuestUser/WinRmHostPortgenuinely having generic, non-identity defaults; (2)vm-fleet-status.ymlwas incorrectly grouped with the two provisioning workflows as taking "every real identity value" as an explicit input, when it actually takes zeroworkflow_dispatchinputs; (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#48exception forworkflow_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 recordedgate="passed"even whenGRYPE_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-unversionedpip/pytest/pytest-cov/pyyamlinstalls to the exact versions a real recent CI run proved against, and fixed a danglingdocs/requirements/srs.mdreference (that path only exists ephemerally during an activestandards-assurance-scan.ymlrun, not as a permanently committed file) in both this workflow andscripts/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-developno-op exception added inv0.3.27was only documented indocs/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 (beforev0.3.9), which were tagged under the prior trunk-based model perADR-0001and have norelease/*branch ancestry - fix
docs/release/release-procedure.md: (1) the GitFlow Branch Rules summary's hotfix merge-back bullet read as an either/or betweendevelopand an active release branch, when the detailed Hotfix Flow steps are additive (alwaysdevelop, plus an active release branch if one exists); (2) the Feature Flow only documented the oldersync-from-fork-<date>branch-naming pattern, omitting thesync-upstream-develop-*/sync-upstream-main-vX.Y.Zpatterns actually used in recent practice, and never explained the post-release fork-sync step that is whydevelop/mainare 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'sinternal/Pipeline.Stages.ps1row 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 ofPublish-DependencyTrack, not a separate preceding stage; (4) thepackage-vagrant-box.py/receipt-scripts row claimed a package-ready receipt verifier exists; it doesn't; (5) thevipm-exit-codes.json/pipeline-config.schema.jsonrow 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) thebuild-virtualbox.ps1/.shrows 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#69and 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 inRegister-WslRunnerKeepAlive.ps1,vm/ubuntu-labview/base-bootstrap.shand 5 other scripts sharing its/SandboxSBOMReporting/SshHostEd25519Fingerprintguest-property path, andRun-WindowsSbom.ps1/Run-LinuxSbom.ps1's own.DESCRIPTIONtext -- beyond what#62already tracked - file
#69:batch-provision.shgives 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 fortoolchain-smoke-test.yml(never actually called in this repo) orTest-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-auditpass (same 3-model delegation, explicitly asked to verify whetherv0.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/#63updated with corrected evidence