release: PRFlow v2.38.0 — corrections and first-visit fixes - #2143
Merged
Conversation
Restores the documentation deployment, closes two verification blind spots, and corrects what a first-time visitor sees. Also regenerates .release/ provenance, which the preceding policy-update commit left inconsistent with the tree. PRFlow-Source-Commit: aeb0afc2342117ac40c153778832febf636ab8ca PRFlow-Artifact-Digest: 2e25c5da40a87f205b6368580f68583392d7aad7d3d9ec2da76299c20b3d6aa9
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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.
A corrections release. Small diff, and it repairs the integrity check on
main.It fixes
main's failing verificationThe preceding
policy-updatecommit edited.github/verify-release.pydirectly on thisbranch without regenerating
.release/, so the digest manifest stopped matching the treeand
distribution-verifyhas been red onmainsince. This release regenerates theprovenance through the exporter, as every release does.
Verified on the candidate: 436 digests OK, 0 failed.
What else it fixes
The documentation site deploys again. The frozen-
DEVFLOW_*advisory moved into thepublished cloud-setup page carrying its generated region's HTML comment delimiters. Those
pages are parsed as MDX, which rejects an HTML comment outright, so the deployment failed
and the site kept serving its previous build. The markers are now MDX comments.
Release verification covers two surfaces it previously skipped. SVG files are text and
can carry anything but were never leak-scanned; the documentation navigation manifest is
JSON, so the markdown link checker never read it, and an entry naming a dropped page would
have published a broken site. Both are checked now, each proven against a planted defect.
First-visit corrections. The CI badge pointed at a workflow this tree no longer carries
and rendered as a broken image. The repository-layout block described the pre-release tree.
/prflow:initwas still titled "DevFlow Init".docs/README.mdcalled itself minimal whileholding the whole documentation site.
SECURITY.mddescribed a.gitignorethis repositorydoes not have.
.gitattributesshipped rules for test fixtures that are not here.A pull-request template, because
CONTRIBUTING.mdexplains that a patch cannot mergeas-is only to a reader who opens it first — and the contribution is still wanted.
The PyYAML floor is published.
>=6was declared nowhere a consumer reads.Diff
437 files, 19 paths changed against
main. Verify it yourself: