Skip to content

docs(cas-contracts): define Pages publication ordering #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
OgeonX-Ai merged 1 commit into from
Jul 6, 2026
Merged

docs(cas-contracts): define Pages publication ordering #17

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/DISTRIBUTION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,16 @@ a schema tag can no longer clobber each other on the single Pages origin.

Repository administrators must configure GitHub Pages to use **GitHub Actions** as its source. Publication uses GitHub's OIDC token and does not require stored deployment credentials.

### Release ordering

GitHub Pages identifies deployments by commit SHA. A release tag created on the
same commit as a just-finished default-branch deployment can therefore produce a
different artifact that Pages treats as the same deployment. After creating a
schema release tag, merge a post-release metadata commit (for example, advancing
the changelog) on the default branch. That deployment runs from a new SHA, sees
the new tag, and publishes the complete immutable release set. Verify both the
immutable manifest and the stable-line index before declaring the release done.

## Custom domain (optional future work)

When `schemas.coding-autopilot.dev` is activated, it must serve the same
Expand Down
Loading