Skip to content

(via norrietaylor): docs: document nightly-provenance gate and override_provenance input in - #900

Merged
macroscopeapp[bot] merged 1 commit into
pr/release-pipelinefrom
macroscope/pr/release-pipeline
Jul 22, 2026
Merged

(via norrietaylor): docs: document nightly-provenance gate and override_provenance input in #900
macroscopeapp[bot] merged 1 commit into
pr/release-pipelinefrom
macroscope/pr/release-pipeline

Conversation

@macroscopeapp

@macroscopeapp macroscopeapp Bot commented Jul 22, 2026

Copy link
Copy Markdown

Summary

Documents the nightly-provenance gate and override_provenance input in the release pipeline documentation.

Changes

  • promote.yml section: Added documentation explaining that scripts/verify-nightly-provenance.sh rejects versions not built by nightly.yml (staged ≠ promotable), and describes the override_provenance emergency input for bypassing this check when necessary.

  • "Promote to stable" runbook: Added an upfront warning step advising users to verify their SHA was nightly-built before starting the multi-hour approval process. Includes guidance on using override_provenance for emergency non-nightly releases.

Why

This documentation helps release engineers understand:

  1. Why a staged version might be rejected during promotion (provenance verification failure)
  2. How to avoid wasting time on the approval process for non-promotable versions
  3. How to handle emergency releases that bypass the normal nightly build flow

Note

Macroscope: Fix It For Me

  • This PR originated from this comment in docs: document the release and install pipeline #867.
  • Since auto-merge is on, Macroscope will merge this PR after waiting for checks to pass.
  • If you'd rather not wait, you can always merge this yourself but no further action from you is currently needed.
  • You can also @mention Macroscope in this PR to request further changes.

Activity

Currently: Auto-merged 4e9bc96

Previously

Note

Document override_provenance input and nightly-provenance gate in promote workflow

Updates release-pipeline.md to document a new nightly-provenance gate in the promote job and its associated override_provenance input parameter.

  • The promote job now runs scripts/verify-nightly-provenance.sh against the target SHA to confirm the version was built by nightly.yml, rejecting manually dispatched or tag-push builds.
  • Setting override_provenance skips this check when needed.
  • The 'Promote to stable' runbook is reorganized to add a preliminary step verifying the SHA is nightly-built, clarify approval order, and note that the provenance check runs before set-channel.sh flips the pointer.

Macroscope summarized ac2f1a2.

@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Free

Run ID: a1f4fcd1-48b1-4d13-9d2f-03c6d713cc9f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@macroscopeapp
macroscopeapp Bot merged commit 4e9bc96 into pr/release-pipeline Jul 22, 2026
2 checks passed
@macroscopeapp
macroscopeapp Bot deleted the macroscope/pr/release-pipeline branch July 22, 2026 04:58
norrietaylor added a commit that referenced this pull request Jul 26, 2026
* docs: document the release and install pipeline

Add docs/internal/release-pipeline.md, a maintainer-facing runbook for the
release/install pipeline: release.yml, the stable/unstable/nightly channels,
staging, promotion, pruning, and the operator steps. Marked internal
(publicly visible in the repo, not published to the docs site).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* docs: document nightly-provenance gate and override_provenance input in release-pipeline.md (#900)

Co-authored-by: macroscopeapp[bot] <170038800+macroscopeapp[bot]@users.noreply.github.com>

* docs: remove the private docs-repo reference from the promote runbook

The reference-docs promotion dispatch named the docs-site repo and its
GitHub App. That repo is private, so this public repo should not announce
it, and the promote pipeline is being reshaped besides. Describe the
`reference-docs-promoted` dispatch abstractly (it triggers a
docs.minimal.dev rebuild) without naming the target repo.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* fix(release): verify smoke tests actually ran in nightly provenance check (#911)

Co-authored-by: macroscopeapp[bot] <170038800+macroscopeapp[bot]@users.noreply.github.com>

* docs: remove em-dashes and fix the version-source binary in the release runbook

* fix(scripts): close the no-op-nightly loophole in the provenance gate

smoke-success is if: always() and skip-tolerant, so a no-op nightly run (SHA
already staged, smokes skipped) still concluded success and could vouch for a
version that was never smoked. The gate now also requires the Linux smoke
jobs themselves to have run and passed; smoke-macos alone may be skipped by
the RUN_MACOS_CI kill-switch. Test fixtures move to name/conclusion pairs and
cover the real no-op shape and the kill-switch shape (31 tests). The runbook
text now states the guarantee precisely, drops the unsourced retirement
claim, and documents the channel-endpoint target override.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: macroscopeapp[bot] <170038800+macroscopeapp[bot]@users.noreply.github.com>
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