docs: weekly documentation audit 2026-08-18 - #22
Draft
krakenhavoc wants to merge 1 commit into
Draft
Conversation
Carries forward the unreleased-entries gap from #19 (opened 2026-07-14, never merged). No PRs merged or opened in this repo in the past week.
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.
Weekly Documentation Audit — 2026-08-18
Supersedes #19 (opened 2026-07-14, never merged — 5 weeks stale). No PRs were merged or opened in this repo between 2026-08-11 and 2026-08-18, so the gap is unchanged from #19; this PR carries it forward unmodified.
Documentation gap
CHANGELOG.md's[Unreleased]section is empty despite:fix: improve release pipeline with auto notes and semver-only triggers) never being logged.Changes made
CHANGELOG.md— added to[Unreleased]: the release-pipeline trigger/notes/make_latestchange (#11), and PKI advisories for SC-098v2 CAA params, Chrome EKU separation, CT mandatory logging, and LE Merkle Tree Certificates (the last of which will require futurechain-path/fullchain-pathchanges once Let's Encrypt's production MTC rollout lands).New docs needed
None this week.
Suggested version bump
v1.2.0 — once MTC compatibility work is scoped and at least one
[Unreleased]item ships.