Repository navigation
Publish reviewable drafts as pre-releases - #3
Merged
Merged
Conversation
The documents are public and under review, but there is no way to hand someone a PDF: releases are cut only from date tags, and a date tag means ratified. Workflow artifacts are not an answer — they need a logged-in GitHub account and expire after ninety days. A `draft-YYYY-MM-DD` tag now publishes the same consolidated PDF as a GitHub pre-release. The two paths are deliberately different at every point a reader might confuse them: the release is flagged as a pre-release rather than Latest, its notes open by saying the documents have not been ratified and point at CHARTER.md §12.1, and the PDF carries the draft tag in the footer of every page where a version number would otherwise sit. The ratified path is untouched. Both still refuse to publish a tag that is not an ancestor of main, so a draft PDF always reflects a real state of the repository rather than someone's working tree. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Timur Bazhirov <timur@exabyte.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The documents are public and under review, but there is no way to hand someone a PDF. Releases are cut only from date tags, and a date tag means ratified (
CHARTER.md§12.1). Workflow artifacts are not an answer — they need a logged-in GitHub account and expire after ninety days.A
draft-YYYY-MM-DDtag now publishes the same consolidated PDF as a pre-release. The two paths differ at every point a reader might confuse them:YYYY.M.D-Ndraft-YYYY-MM-DDdraft-YYYY-MM-DDBoth paths still refuse to publish a tag that is not an ancestor of
main, so a draft PDF always reflects a real state of the repository rather than someone's working tree.Not part of this change, but worth recording: the branch protection on
mainrequired a check namedpdf, while the job is namedbuild. No pull request could ever have merged. Corrected tobuildandsign-off-check.🤖 Generated with Claude Code