docs: make Flutter Versions a general Flutter reference - #632
Merged
Conversation
eseidel
enabled auto-merge (squash)
August 25, 2026 23:44
The page ranks around position 8 for the "what Flutter version is current" query cluster but answered a Shorebird-specific question instead. Restructure it so the top half is useful to any Flutter developer and the Shorebird-specific material moves below it. - Lead with the current stable release, in a callout, as one plain sentence that a search engine or assistant can lift directly. - Add a table of the newest patch of each recent release, with its Dart SDK version, release date, and headline changes. Five rows show by default; all ten ship in the HTML so crawlers read the whole table. - Generate the version data from Flutter's release feeds into src/data/flutter-releases.json via `npm run update-flutter-releases`. A daily workflow fails the build when it falls behind stable. - Keep the existing Shorebird version notes, unchanged, under a new "Shorebird and Flutter versions" heading. The two section anchors Google indexes separately keep their ids. Highlights are hand-written in src/data/release-highlights.ts, since the feeds carry no information about what changed.
AbhishekDoshi26
force-pushed
the
docs/flutter-versions-reference
branch
from
August 27, 2026 07:06
89a32bd to
3c5dedc
Compare
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.
Status
READY
Description
/getting-started/flutter-version/ranks around position 8 for the "what Flutter version is current" query cluster, but the page answers a Shorebird-specific question instead. This restructures it so the top half is useful to any Flutter developer and the Shorebird material sits below it.Page
#supported-flutter-versionsand#use-a-different-flutter-versionkeep their ids — Google indexes both as separate results.Data
scripts/update-flutter-releases.mjsmerges Flutter's three platform release feeds intosrc/data/flutter-releases.json(one row per release, newest patch, Dart version, dates). Run it withnpm run update-flutter-releases. No generation timestamp, so a no-op run produces no diff..github/workflows/flutter-releases.yamlruns daily and fails when the committed file has fallen behind stable, with a message naming the new version. It does not open a PR. Both paths were exercised locally.src/data/release-highlights.ts, summarized from Flutter's own release announcements — the feeds carry versions and dates but nothing about what changed. A release with no entry renders a dash.Note that this is all separate from
src/consts.ts, which tracks the Flutter version Shorebird ships and is still bumped by hand. The page distinguishes the two.Checks
npm run build,format:check, cspell, Vale, and the component-label lint all pass locally. Verified the table and callout in light and dark, and the toggle in a browser.Follow-ups, not in this PR