feat: add dart 3.13 and flutter 3.47 runtimes

[lohanidamodar]

Registers the Dart 3.13 and Flutter 3.47 runtimes added in open-runtimes #552 and #553, both shipped in release 0.13.24.

Part of CLO-4756. One line per runtime, directly under the previous version.

$dart->addVersion('3.13', 'dart:3.13.1', 'openruntimes/dart:'.$this->version.'-3.13', [System::X86, System::ARM64, System::ARMV7, System::ARMV8]);
$flutter->addVersion('3.47', 'ghcr.io/adrianjagielak/flutter:3.47.1', 'openruntimes/flutter:'.$this->version.'-3.47', [System::X86, System::ARM64]);

Flutter stays on ghcr.io/adrianjagielak/flutter: ghcr.io/cirruslabs/flutter publishes nothing past 3.44.0 — no stable tag for 3.45, 3.46 or 3.47, only .pre betas. That registry switch was already made for 3.44 in #104.

Flutter 3.47.1 bundles Dart 3.13.1, so the two versions belong together.

Verification

$ php -l src/Runtimes/Runtimes.php
No syntax errors detected

$ ./vendor/bin/phpunit
OK (11 tests, 1208 assertions)

Resolved entries check out against getAll('v5'):

dart-3.12      image=openruntimes/dart:v5-3.12     base=dart:3.12.0
dart-3.13      image=openruntimes/dart:v5-3.13     base=dart:3.13.1
flutter-3.44   image=openruntimes/flutter:v5-3.44  base=ghcr.io/adrianjagielak/flutter:3.44.0
flutter-3.47   image=openruntimes/flutter:v5-3.47  base=ghcr.io/adrianjagielak/flutter:3.47.1

Before merging

The open-runtimes publish workflow for 0.13.24 is still queued, so openruntimes/dart:v5-3.13 and openruntimes/flutter:v5-3.47 are not on Docker Hub yet — both currently 404. Worth confirming each resolves with both amd64 and arm64 manifests before this merges, since publish silently skips a target whose manifest is single-platform.

Also note the publish runs for the two previous releases (0.13.22, 0.13.23) both ended red, so the tags are worth checking explicitly rather than assuming the release cut them.

[lohanidamodar]

Image gate met. Both tags are now live with the required platforms:

openruntimes/dart:v5-3.13     OK ['amd64', 'arm64']  pushed 2026-08-24T04:42:49
openruntimes/flutter:v5-3.47  OK ['amd64', 'arm64']  pushed 2026-08-24T04:43:20

Their publish jobs in the 0.13.24 release run both completed successfully. The overall run is red, but that is the long-standing java-8/11/17 arm64 failures — fail-fast: false lets each target publish independently, so it does not affect these.

This is ready to merge whenever you are. The next step needs a new tag (currently 0.20.4), not just the merge, before the appwrite/appwrite composer bump can follow.

[greptile-apps]

Greptile Summary

Registers the newly supported Dart 3.13 and Flutter 3.47 runtimes.

• Adds Dart 3.13.1 with the existing Dart architecture set.
• Adds Flutter 3.47 backed by Debian 12.15 base metadata and the separate Open Runtimes Flutter image.
• No code has changed since the previous review.

Confidence Score: 5/5

The PR appears safe to merge, with no outstanding findings in the current code.

The prior Flutter SDK finding was manually resolved after upstream evidence established that Debian is intentional base metadata and that the separate Open Runtimes image installs and contains Flutter 3.47.1. No changes were made after that review, and no new issues or repository-rule violations were identified.

Important Files Changed

Filename	Overview
src/Runtimes/Runtimes.php	Adds Dart 3.13 and Flutter 3.47 runtime registrations; the intentionally Debian-based Flutter metadata is consistent with the supplied upstream implementation evidence.

_{Reviews (3): Last reviewed commit: "fix: correct flutter 3.47 base image to ..." | Re-trigger Greptile}

[ChiragAgg5k]

@greptile review

Please re-evaluate current head 66d9db9 with the upstream source evidence in #109 (comment) . Flutter 3.47 intentionally uses Debian base metadata: upstream c453801a180de022454fae30bea0556fcd9559f3 installs Flutter 3.47.1 in its Dockerfile and publishes the separate Open Runtimes image. The prior SDK-missing finding is a false positive, not a reason to revert the correct base.

[ChiragAgg5k]

Reviewed the runtime registrations and upstream Flutter image evidence. Greptile is 5/5 with no unresolved threads; PHPUnit, Pint, PHPStan, and all PR checks pass.