Publish the v26.7.1 release announcement - #119
Merged
vpetersson merged 1 commit intoJul 30, 2026
Merged
Conversation
Removes draft: true from the v26.7.1 post. The flag was set intentionally in sbomify#118 so that merging would not publish the post before the copy had been reviewed, on the assumption it would be removed as a separate step. That step was missed, so the post has been on master since 12:55 without appearing on the site: Hugo excludes drafts from production builds, and only the nightly/deploy build with --buildDrafts would have picked it up. Verified with a clean production build (no --buildDrafts): the post renders, and appears in the blog index, the RSS feed, the sitemap, and on the homepage.
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.
Removes
draft: truefrom the v26.7.1 post. One line.Why the post is not showing
The flag was deliberate in #118 — it meant merging would not publish the post before the copy was reviewed, with removal intended as a separate step. That step was missed, so since #118 merged at 12:55 the post has been on
masterbut invisible: Hugo excludes drafts from production builds.Confirmed:
A note on verification, because my first check was wrong: a stale
public/from an earlier--buildDraftsrun made it look like the production build included the post. Hugo does not cleanpublic/between builds. Withrm -rf publicfirst, the difference is unambiguous:hugo --minify --environment productionhugo --minify --environment production --buildDraftsAfter this change
Clean production build, no
--buildDrafts:feed.xmlsitemap.xmldprint checkclean.Merging this will publish the post on the next deploy, so it is worth a final read of the copy first — particularly the vulnerability-count section, which tells users their totals will drop.