V2.0.0/fix docker staging

[gimlichael]

No description provided.

[greptile-apps]

Greptile Summary

The PR preserves image and SBOM artifact identity when failed publication or attestation jobs are rerun and clarifies registry credential requirements.

• Exposes artifact names as outputs of the container build job.
• Uses those outputs in all downstream image and SBOM consumers.
• Documents staging and Docker Hub secret names and token expectations.

Confidence Score: 5/5

The PR appears safe to merge with artifact identity consistently propagated through the container workflow.

Downstream jobs all declare the build job as a dependency, consume names produced from the same values used during upload, and remain gated on successful prerequisite jobs.

Important Files Changed

Filename	Overview
.github/workflows/ci-pipeline.yml	Exports build-attempt artifact names and consistently passes them to downstream publishing, promotion, and attestation jobs.
README.md	Clarifies environment secret names, Docker Hub token requirements, and artifact reuse during failed-job reruns.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  B[Container build] -->|image artifact name| P[Staging publish]
  B -->|SBOM artifact name| A[Staging attestation]
  P --> D[Docker Hub promotion]
  B -->|image artifact name| D
  B -->|SBOM artifact name| H[Docker Hub attestation]
  D --> H

Loading

_{Reviews (1): Last reviewed commit: "💬 clarify Docker image deployment and s..." | Re-trigger Greptile}