fix(blog): keep the roadmaps below the release posts - #8409
Merged
alexander-akait merged 1 commit intoSep 14, 2026
Merged
alexander-akait merged 1 commit into
alexander-akait merged 1 commit into
Conversation
The blog list is ordered by date, so a roadmap published between two releases sat among them: roadmap 2026 (2026-02-04) above webpack 5.105 (2026-02-03). Group the roadmaps after every other post, where the date comparison then orders them from the highest year down.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
UlisesGascon
approved these changes
Sep 14, 2026
This branch was successfully deployed
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
2 participants
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
The blog list is ordered by date, so a roadmap published between two releases sits among them: Roadmap 2026 (2026-02-04) renders above Webpack 5.105 (2026-02-03) in the sidebar and on
/blog/. Roadmaps outlive the releases they plan, so they are now grouped after every other post, where the existing date comparison orders them from the highest year down.Order after the change:
The RSS feed is left alone, since it is a chronological feed with per-item
pubDate.What kind of change does this PR introduce?
fix
Did you add tests for your changes?
Yes, a case in
src/utilities/content-tree-enhancers.test.mjscovering index first, releases newest first, roadmaps last from the highest year down. It fails without the change.Does this PR introduce a breaking change?
No.
If relevant, what needs to be documented once your changes are merged or what have you already documented?
n/a
Use of AI
Claude Code was used to locate the sorting logic, write the change and its test, and verify the resulting order by building the content tree locally. Every change was reviewed before pushing, and the full unit suite passes.
🤖 Generated with Claude Code
https://claude.ai/code/session_012ee7dGaRGKqYPxUzFEEU65
Generated by Claude Code