docs: refresh public release digest and retain merge dates - #213
Merged
Conversation
abrichr
force-pushed
the
docs/auto-sync
branch
from
September 10, 2026 20:39
9279636 to
6d0aa90
Compare
abrichr
changed the title
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
1 participant
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 release changelog now includes Flow 1.35.1. The weekly digest uses the current public merged-PR feed and shows each merge date. Its template previously read
merged_at, while the GitHub CLI returnsmergedAt, leaving every date blank.A failed, timed-out, unavailable, or invalid GitHub CLI response now stops generation before it replaces the existing digest. An empty successful response still means that a repository has no recent merged PRs.
Both pages were generated with the existing scripts on 10 September. All 11 included repositories were confirmed public; Cloud remains excluded. This refresh used the raw PR list and made no LLM call.
Validation: 25 focused generator tests, docs validation, and a strict MkDocs build pass. The failure tests preserve a previous digest, and the date test carries the CLI response through the real template. Merging this PR publishes the docs through the existing Pages workflow.
Updated by an agent session, not the founder.