chore(release): 0.0.10

[anilcancakir]

Floor-only release for the 2026-10-13 batch. Wave 5, after magic 0.0.28 (live). No source change.

What ships

Every sibling floor names this batch's release. magic moves ^0.0.27 to ^0.0.28, fluttersdk_dusk ^0.0.19 to ^0.0.20, fluttersdk_telescope ^0.0.10 to ^0.0.12 and fluttersdk_wind ^1.8.1 to ^1.8.4. The old ranges already admitted the new versions, so a fresh pub get resolves nothing differently; what changes is that the floors name the releases this package is verified against. None of magic 0.0.28, dusk 0.0.20, telescope 0.0.11 and 0.0.12 or wind 1.8.2 to 1.8.4 is breaking for this package: dusk 0.0.20 and telescope 0.0.12 only move to artisan 0.0.20, whose connected commands print one retry line and exit 75 when an extension is not registered yet; wind 1.8.2 restores the click cursor under hover:, which the preview catalogue's navigation rows use, and 1.8.3 adds autofillHints, which this package does not call. The README install snippet quotes the new devtools, dusk and telescope pins. (pubspec.yaml, README.md)

Floors

Dependency	From	To
magic	^0.0.27	^0.0.28
fluttersdk_dusk	^0.0.19	^0.0.20
fluttersdk_telescope	^0.0.10	^0.0.12
fluttersdk_wind	^1.8.1	^1.8.4

Stamps

pubspec.yaml 0.0.9 to 0.0.10; README.md install snippet (devtools, dusk and telescope pins); CHANGELOG section 0.0.10 dated 2026-10-13. magic's plugin-devtools.md was stamped v0.0.10 ahead of this release in magic 0.0.28.

git grep -nF 0.0.9 -- ':!CHANGELOG.md' ':!*.lock' and a grep for each old floor are empty.

Gates

Run against the magic 0.0.28 release commit through a temporary override, then re-resolved on the hosted graph once magic 0.0.28 was live.

• flutter analyze --no-fatal-infos: no issues.
• dart format --set-exit-if-changed .: 18 files, 0 changed.
• flutter test: +141, all passed.
• flutter pub publish --dry-run on the hosted graph: 0 warnings.

Tag

git tag 0.0.10 <merge-oid> && git push origin 0.0.10

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!