Repository navigation
release: 0.0.40 - #175
Merged
Merged
release: 0.0.40#175
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
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.
Release of the catalogue-driven billing screen and the social sign-in client that landed on main since 0.0.38. This is the last wave of the 2026-10-09 batch, after magic 0.0.27, magic_notifications 0.3.8 and magic_payments 0.0.8 (all live).
What ships
products: both rails purchase by catalogue product key, a store build offers and prices only the products its own store carries, and a store purchase reports the rail's own change timing. BREAKING for a host that implementsWebBillingServiceorStoreBillingService, or a slot that readMagicStarterPlan.monthly,annualorcurrency.MagicStarterSocialAuthbridge, connected accounts, step-up confirmation and scheduled account deletion. This was tagged 0.0.39 from that merge commit; its CHANGELOG section is already in place.Floors
magic_payments^0.0.7^0.0.8(a real requirement: product-key purchases,PurchaseContext,lastChangeTiming)magic^0.0.24^0.0.27magic_notifications^0.3.6^0.3.8fluttersdk_wind^1.8.0^1.8.1fluttersdk_artisan^0.0.17^0.0.19Each pubspec comment that explains a floor keeps its reason and gains the batch note. magic_payments 0.0.8 is BREAKING and this package adopts it in this release (#174); none of magic 0.0.25 to 0.0.27, magic_notifications 0.3.7 and 0.3.8, wind 1.8.1 or artisan 0.0.18 and 0.0.19 is breaking.
Stamps
pubspec.yaml,CLAUDE.md**Version:**, and theREADME.mdanddoc/getting-started/installation.mdinstall snippets..github/ISSUE_TEMPLATE/bug_report.yml: the Magic Starter Version field reads0.0.40and the Magic Framework Version field, which still read1.0.0-alpha.3, reads0.0.27.magicStarterVersion, which is test-guarded.magicNotificationsConstraint(^0.3.8), which has a parity test with the pubspec floor.plugin-starter.mdv0.0.40 ahead of this release (checked by hand: the worktree skipsskill_reference_stamp_test).git grep -nF 0.0.39 -- ':!CHANGELOG.md' ':!*.lock'is empty, and so is a grep for each old floor.Gates
Run on the hosted graph (no
pubspec_overrides.yaml; resolved magic 0.0.27, magic_notifications 0.3.8, magic_payments 0.0.8, wind 1.8.1, artisan 0.0.19):dart format --output=none --set-exit-if-changed .: 388 files, 0 changed.flutter analyze: no issues.flutter test: +1884, with the one skip (skill_reference_stamp_test, no sibling checkout beside the worktree).flutter pub publish --dry-run: 0 warnings.Tag