Skip to content

v1.2.0 — reusable implementation evidence guard

Choose a tag to compare

View all tags
@stevenknowswhy stevenknowswhy released this 01 Aug 11:21
v1.2.0
124acd1

This release adds a dependency-free GitHub Action for validating a buyer-approved implementation-evidence manifest.

What it checks:

  • a named product surface, repository, and build revision;
  • the source of the approved implementation requirement and approved notice text;
  • a named route, component, and expected behavior;
  • at least one passing technical check; and
  • at least one explicit known limitation.

The Action rejects manifests that include a legal determination or top-level compliance assertion. A passing result means only that the required implementation fields and passing checks are present. It is not an applicability decision, legal opinion, audit, certification, or compliance guarantee. The bundled evidence remains fictional and is not a client result.

Use it with:

uses: stevenknowswhy/article50-launch-patch-proof@v1.2.0
with:
  manifest-path: example/evidence-example.json

AI assisted the implementation and release notes. The repository test workflow passed on the release commit.

Assets 2
Loading