Add v26.7.1 release announcement post - #115
Closed
vpetersson-bot wants to merge 1 commit into
Closed
Conversation
Drafts the release post for v26.7.1, following the house pattern for release announcements (byline Viktor Petersson, "The One That ..." title, TL;DR block, per-theme sections, Getting Started). Leads on VEX, which is the substantive change in this release: three formats, in-product triage, Dependency-Track sync, and scheduled drift detection. Then CBOM ingestion breadth (framed as closing the gap left by v26.7.0), Trust Center exposure, and the vulnerability-count posture fix, which is called out separately because users will see their totals drop. Left as `draft: true` so merging does not publish it before it has been reviewed -- delete that line to ship. Verified: dprint clean, Hugo builds, and every internal link resolves (previous release post, /features/ trust-center/, /authors/vpetersson/, all tag pages).
Contributor
Author
|
Superseded by #118, which folds this together with the other two v26.7.1 site changes into a single PR. The commit is carried over unchanged (cherry-picked with |
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.
Draft release post for v26.7.1, matching the existing release-announcement pattern.
Conventions followed
Modelled on the v26.7.0 post and the two before it:
YYYY-MM-DD-announcing-sbomify-vXX-Y-Z-the-one-that-...filename and matchingslugtitle,description,author.display_name,categories: [announcement],tags,tldr,date— nokeywords, consistent with the other release posts (only 6 of 91 posts use it)---separators between themes,## Getting Startedlast with hosted / self-hosted split and a link to the GitHub release notesStructure
VEX leads, since it is the substantive change: three formats (CycloneDX / OpenVEX / CSAF), in-product triage, Dependency-Track sync, scheduled drift detection. The post explains why VEX matters before listing features, the way the v26.7.0 post introduced CBOM.
Then CBOM ingestion breadth — framed as closing the gap v26.7.0 left, with a link back to that post — Trust Center exposure, and a section on the vulnerability-count fix.
That count fix gets its own section deliberately: users will see their totals drop, in many cases sharply, and it is better to explain that in advance than to field confused questions. The post is explicit that nothing was fixed by the change itself, the number is just accurate now.
Design refresh, API/security, and a short "Under the Hood" on CI and error-tracking round it out.
Verification
bun run lint:markdown— cleanhugo --minify --environment production --buildDrafts— builds, 454 pages/features/trust-center/,/authors/vpetersson/, and all seven tag pages<title>, byline and TL;DR block all correct (the escaped quotes in the title render properly)Two things to note
draft: trueis set, so merging will not publish it. Remove that line when you are happy with the copy. I defaulted to draft since you asked for a draft, and the deploy workflow publishes on push tomaster.The commit is authored by
vpetersson-bot, not Viktor. The post byline is Viktor Petersson as requested, but I did not forge git authorship. Reassign or amend the commit if you would rather it be attributed to you.