Skip to content

Add attested provenance workflow for the Gemini Nano demo bundle#9

Merged
OgeonX-Ai merged 6 commits into
masterfrom
codex/provenance-gemini-nano-attestation
Jul 9, 2026
Merged

Add attested provenance workflow for the Gemini Nano demo bundle#9
OgeonX-Ai merged 6 commits into
masterfrom
codex/provenance-gemini-nano-attestation

Conversation

@OgeonX-Ai

@OgeonX-Ai OgeonX-Ai commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Summary

This PR adds a dedicated provenance workflow for gemini-nano that validates the existing demo surfaces, builds the docs site, packages a deterministic demo bundle, attests it, verifies the attestation in the same run, and publishes the bundle artifacts.

Changes

  • add .github/workflows/provenance.yml
  • validate the existing Python and Node demo components before packaging
  • build the MkDocs site, archive the docs plus component entrypoints/manifests, and attest the resulting tarball
  • publish the bundle and attestation artifacts for later evidence capture
  • align the README Python entrypoint with the real api-server/server.py file

Why

The portfolio provenance ledger currently marks Coding-Autopilot-System/gemini-nano as evidence-only with no attestation workflow. This PR upgrades one clean repo to real attestation coverage instead of leaving the root ledger to describe future intent.

Validation

  • static local sanity check of .github/workflows/provenance.yml
  • full end-to-end workflow validation is expected from GitHub Actions on this PR

Risks

  • the bundle attests a deterministic demo/archive artifact, not a package published to an external registry
  • workflow success depends on the existing MkDocs and component validation steps staying green on GitHub runners

Related

Reviewer notes

Start with .github/workflows/provenance.yml. The key review points are the bundle contents, the attestation verification step, and whether the chosen artifact is the right provenance boundary for this repo.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7aeba81f02

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .github/workflows/provenance.yml Outdated
chrome-bridge/package.json \
chrome-bridge/package-lock.json \
chrome-demo/index.html \
python-mediapipe/requirements.txt

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Include the MediaPipe demo entrypoint in the bundle

When a change only touches python-mediapipe/run_nano.py, this workflow still runs because python-mediapipe/** is in the path filter, but the archive only includes python-mediapipe/requirements.txt. The bundled README/docs tell users to run python-mediapipe/run_nano.py, so the published and attested demo archive omits the MediaPipe demo code it claims to cover; add run_nano.py or the whole directory to the tarball so those changes are actually shipped and attested.

Useful? React with 👍 / 👎.

root added 3 commits July 9, 2026 23:04
Replace brittle pytest collection on the manual smoke script with a real unit suite for alias resolution and model catalog exposure. Align CI and provenance verification so both workflows use the same non-Ollama Python checks.
Update the chrome-bridge CI job to the current setup-node pin already used by the provenance workflow so GitHub stops forcing the deprecated Node 20 action runtime.
Align the CI Python setup step with the current action pin already used in the provenance workflow to remove the remaining deprecated Node 20 runtime warning.
@OgeonX-Ai
OgeonX-Ai merged commit feb71cf into master Jul 9, 2026
9 checks passed
@OgeonX-Ai
OgeonX-Ai deleted the codex/provenance-gemini-nano-attestation branch July 9, 2026 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant