Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions doc/realizations.md
Original file line number Diff line number Diff line change
Expand Up @@ -420,6 +420,21 @@ production deployment can avoid by knowing about it.
Items discovered while building the production Rust port; each is
a trap the next developer should not have to step in.

- **A system Flutter upgrade can block every push; the Flutter steps use the
pinned SDK when one is installed (2026-11-18).** The machine's Flutter went
to 3.50, whose analyzer flags `package:flutter/material.dart` as deprecated
(Material moved to the pub package `material_ui`), so `flutter analyze`
failed in the pre-push gate while CI (3.44.4) was green. Moving to
`material_ui` is blocked by the ecosystem: even `google_fonts` 8.2.1 still
builds on the SDK's Material, and `material_ui`'s classes are distinct
types (a google_fonts `TextTheme` is not a material_ui one). And the
explorer image's build base, `ghcr.io/cirruslabs/flutter`, publishes
nothing newer than 3.44.0. So `scripts/check.sh` now puts
`$TRITON_FLUTTER_HOME`, else `~/.local/share/flutter-<pin>`, first on PATH
for the Flutter steps (install line in the script); revisit the 3.50 move
when google_fonts and co. support `material_ui`, with a self-installed
Flutter in the explorer image.

- **A short card text is not enough for ChatGPT: slim `structuredContent`
too (2026-11-18).** Live on the Nidorel demo, ChatGPT declared MCP Apps
(`card_host: true` in the per-call log line) and so received the one-line
Expand Down
16 changes: 16 additions & 0 deletions scripts/check.sh
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,22 @@ step_capture() {

FLUTTER_PIN=3.44.4 # keep in step with ci.yml's flutter-version

# The Flutter steps run on the CI-pinned SDK when one is installed, so a newer
# system Flutter (whose analyzer may flag what the pin does not) never blocks a
# push: $TRITON_FLUTTER_HOME, else ~/.local/share/flutter-$FLUTTER_PIN, else
# the `flutter` on PATH (with the note below). Install the pin once with
# git clone --depth 1 --branch "$FLUTTER_PIN" https://github.com/flutter/flutter.git \
# ~/.local/share/flutter-"$FLUTTER_PIN"
use_pinned_flutter() {
local home="${TRITON_FLUTTER_HOME:-$HOME/.local/share/flutter-$FLUTTER_PIN}"
if [ -x "$home/bin/flutter" ]; then
PATH="$home/bin:$PATH"
export PATH
fi
}

flutter_version_note() {
use_pinned_flutter
local v
v="$(flutter --version 2>/dev/null | awk 'NR==1 {print $2}')"
if [ "$v" != "$FLUTTER_PIN" ]; then
Expand Down Expand Up @@ -100,6 +115,7 @@ step_flutter_explorer() {

# `--no-wasm-dry-run`: skips the extra wasm compile that OOMs the CI runner.
step_flutter_web() {
use_pinned_flutter
(cd apps/explorer && flutter build web --release --no-wasm-dry-run)
}

Expand Down
Loading