Skip to content

v1.4.1 — post-merge browser QA

Choose a tag to compare

@cderinbogaz cderinbogaz released this 20 Aug 14:00
6abf457

Juror post-merge browser QA is ready for protected staging workflows.

Highlights:

  • plan and execute affected browser journeys against a verified merged deployment
  • run in a sandboxed, public multi-architecture QA image with provenance and SBOM attestations
  • bootstrap authenticated staging sessions and bind secret browser headers to exact trusted origins
  • select a dedicated GitHub deployment environment while preserving staging as the security tier
  • preserve valid empty evidence payloads during report finalization
  • publish the exact packed npm tarball through the corrected trusted-publishing path

Full changes: #62, #67, #70, and #71.