Skip to content

fix(docs): verify future release tag against candidate source - #724

Merged
jeremi merged 1 commit into
mainfrom
agent/release-evidence-candidate-gate
Aug 12, 2026
Merged

fix(docs): verify future release tag against candidate source#724
jeremi merged 1 commit into
mainfrom
agent/release-evidence-candidate-gate

Conversation

@jeremi

@jeremi jeremi commented Aug 12, 2026

Copy link
Copy Markdown
Member

Summary

  • let the docs evidence-link gate recognize only the exact source tag emitted by the newest validated release manifest
  • when that tag is not published yet, verify its repository paths against the selected candidate source instead of creating the immutable tag early
  • keep every other missing tag fail-closed and return to direct tag verification as soon as the tag exists
  • document the pre-publication exception and its protected-main boundary

This is a train-independent prerequisite for release PR #723. It must land before the v0.20.0 release metadata.

Verification

  • node --test scripts/check-evidence-links.test.mjs (16 passed)
  • npm run check:evidence-links (66 links)
  • npm run check (full docs gate on the v0.20 release branch)
  • git diff --check

Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
@jeremi
jeremi merged commit a5f831b into main Aug 12, 2026
30 checks passed
@jeremi
jeremi deleted the agent/release-evidence-candidate-gate branch August 12, 2026 09:41

@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: 9d8216228f

ℹ️ 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".

- every linked repository path exists at that exact tag or commit
- every root-relative documentation route exists at the selected source commit

The exact source tag of the newest validated release manifest is the only

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Add the required DCO sign-off

The reviewed commit message has no Signed-off-by: trailer, so it violates the repository's mandatory DCO policy and will be rejected by the DCO gate; recreate the commit with git commit -s.

AGENTS.md reference: AGENTS.md:L274-L274

Useful? React with 👍 / 👎.

Comment on lines 217 to +221
if (!gitObjectExists(repoRoot, `${commitish}^{commit}`, gitCommand)) {
return `references missing Git commit or tag ${ref}`;
if (ref !== candidateTag || !gitObjectExists(repoRoot, `${sourceRef}^{commit}`, gitCommand)) {
return `references missing Git commit or tag ${ref}`;
}
commitish = sourceRef;

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 Distinguish a missing tag from a non-commit tag

When the candidate ref exists but cannot peel to a commit, such as when refs/tags/v9.9.9 points to a blob or its target commit is absent from an incomplete checkout, this lookup fails and the branch silently substitutes sourceRef. I reproduced this with a blob tag: the check accepted evidence at v9.9.9 against HEAD even though that tag already existed, leaving the claim unanchored at its stated tag; check whether the tag ref itself exists separately and reject an existing tag that cannot resolve to a commit.

AGENTS.md reference: docs/site/AGENTS.md:L25-L28

Useful? React with 👍 / 👎.

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