Clarify that the Latest Releases page isn't a complete release list - #704
Open
harshasiddartha wants to merge 1 commit into
Open
Clarify that the Latest Releases page isn't a complete release list#704harshasiddartha wants to merge 1 commit into
harshasiddartha wants to merge 1 commit into
Conversation
The page only lists releases that have written-up notes, and the newest of those is from February 2025, which makes the project look inactive. Add a short line under the heading pointing to the GitHub releases for the full, current list.
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.
Addresses drizzle-team/drizzle-orm#6101.
The
/docs/latest-releasespage renders every entry undersrc/content/docs/latest-releases/, and the two newest aredrizzle-orm-v1beta2(2025-02-12) anddrizzle-orm-v0.32.2/drizzle-kit-v0.23.2(2024-08-05). Since nothing has been added since, the page reads as if the last release was over a year ago, while the actual latest release on GitHub is much more recent. As the reporter put it, it makes the project look abandoned.This adds one line under the heading explaining that the page only covers releases with written-up notes, and linking to the GitHub releases for the full list:
The alternative the issue also mentions is backfilling the page with every release since 0.32.2, or dropping it entirely and redirecting to GitHub. Both are calls for the team to make, so I went with the smallest change that stops the page from misleading people. Happy to switch to either if you'd prefer.
Styling follows the existing conventions in the component (scoped styles,
html.darkoverride, mobile size in the existing media query), andrel="nofollow noreferrer"for the external link to match the rest of the repo.Verification:
pnpm install,npx astro check(0 errors, 0 warnings, 11 pre-existing hints),pnpm test(29 passed), and checked the rendered page onastro dev.