feat(blog): npm supply-chain compromise postmortem + gradient cover fallback#913
Merged
Merged
Conversation
…allback Adds the 2026-05-11 postmortem. Posts without a header image now render a deterministic slug-seeded muted gradient on both the BlogCard and the post page so they ship without a hand-authored cover asset.
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.
Summary
bg-gray-100 dark:bg-gray-900base + ring + the slug-derived gradient asbackgroundImage.aspect-videoslot when there's noheaderImage.aspect-[5/2] rounded-2xlgradient above the title when there's noheaderImage.The postmortem itself contains no
line, so it picks up the gradient on both the blog index and the post page automatically. Existing posts (all of which have a header image) are unaffected.Test plan
/blog/npm-supply-chain-compromise-postmortemin both light and dark mode — gradient renders above the title, no console or server errors/blog— postmortem's BlogCard shows the gradient in place of the imageog:imagemeta tag — follow-up could route to a server-side OG endpoint)