Found during P0.3 public-demo advisory release-evidence rehearsal (#100).
git ls-remote --tags https://github.com/ThreeMoonsLab/agents-shipgate.git refs/tags/v0.10.0 refs/tags/v0.10.0^{} returned no tag, while public docs and example CI treat v0.10.0 as current. The rehearsal had to pin ThreeMoonsLab/agents-shipgate@5ba36d90549086ca4b4c5b40a8261ac468d2acee instead.
Why it matters: first-contact advisory CI should be copy-pasteable and reproducible. A missing tag turns setup into a GitHub Action resolution failure or forces users to know which commit to pin.
Acceptance criteria:
- Either publish the
v0.10.0 tag/release, or update public guidance to use an available ref.
- Ensure examples that mention
ThreeMoonsLab/agents-shipgate@v0.10.0 are valid against GitHub refs before release.
Found during P0.3 public-demo advisory release-evidence rehearsal (#100).
git ls-remote --tags https://github.com/ThreeMoonsLab/agents-shipgate.git refs/tags/v0.10.0 refs/tags/v0.10.0^{}returned no tag, while public docs and example CI treatv0.10.0as current. The rehearsal had to pinThreeMoonsLab/agents-shipgate@5ba36d90549086ca4b4c5b40a8261ac468d2aceeinstead.Why it matters: first-contact advisory CI should be copy-pasteable and reproducible. A missing tag turns setup into a GitHub Action resolution failure or forces users to know which commit to pin.
Acceptance criteria:
v0.10.0tag/release, or update public guidance to use an available ref.ThreeMoonsLab/agents-shipgate@v0.10.0are valid against GitHub refs before release.