Skip to content

chore(release): 0.0.9 - #24

Merged
anilcancakir merged 1 commit into
masterfrom
chore/release-0.0.9
Oct 9, 2026
Merged

anilcancakir merged 1 commit into
masterfrom
chore/release-0.0.9

Conversation

@anilcancakir

Copy link
Copy Markdown
Member

Floor-only patch, 0.0.8 to 0.0.9. This is wave 3 of the 2026-10-09 batch, after magic 0.0.27, dusk 0.0.19 and telescope 0.0.10 (all live).

What ships

Every sibling floor names this batch's release: magic ^0.0.24 to ^0.0.27, fluttersdk_dusk ^0.0.17 to ^0.0.19, fluttersdk_telescope ^0.0.9 to ^0.0.10, fluttersdk_wind ^1.8.0 to ^1.8.1. The old ranges already admitted these versions, so a fresh pub get resolves nothing differently. None of the upstream releases this crosses is breaking (magic 0.0.25 to 0.0.27, dusk 0.0.18 and 0.0.19, telescope 0.0.10, wind 1.8.1).

Stamps

CHANGELOG.md, README.md (install snippet: devtools, dusk and telescope pins), pubspec.yaml

git grep -nF 0.0.8 -- ':!CHANGELOG.md' ':!*.lock' and a grep for each old floor come back clean, apart from deliberate historical mentions. magic's reference page for this package is stamped v0.0.9 in magic 0.0.27 (fluttersdk/magic#219).

Gates

Run twice: first against magic's 0.0.27 release branch and the dusk 0.0.19 and telescope 0.0.10 release branches through a temporary pubspec_overrides.yaml, then with no overrides against the hosted graph once they were live:

  • dart format --set-exit-if-changed .: 0 changed.
  • flutter analyze --no-fatal-infos: no issues.
  • flutter test: 141 passed.
  • flutter pub publish --dry-run: no warnings.

Tag

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

@codecov

codecov Bot commented Oct 9, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@anilcancakir
anilcancakir merged commit f5b6060 into master Oct 9, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant