chore(release): 0.0.3 (magic ^0.0.6) - #13
Merged
Merged
Conversation
Releases the socket-driven notification state added in #12: `Notify.startRealtime()` takes the bell off its 30-second timer and onto the app's broadcast connection, with polling kept as the fallback in both directions (no driver configured, or a socket that dropped). The `magic` floor moves to `^0.0.6` with it, for `Echo.connection`. That accessor is what lets the realtime path tell an open connection from a closed one, and without it magic's Reverb driver opens a SECOND WebSocket on a redundant `connect()` rather than refusing. A `0.0.z` caret pins the patch digit, so `^0.0.5` resolved exactly 0.0.5, which has no such accessor. **This release does not break the existing consumers, and does not reach them either.** `magic_starter` and `magic_example` both require `magic_notifications: ^0.0.2`, which under the same `0.0.z` caret rule means `<0.0.3`: they keep resolving 0.0.2 and are untouched. Adopting the feature there is a bump in each of those repositories, which also drags their own release train, so it is deliberately not part of this commit. `uptizm` needs nothing: it consumes this package by path, both locally and in CI. Also corrects two version pins that were already stale before this release: the README install snippet (0.0.2) and `CLAUDE.md`'s header, which still said 0.0.1. Verified with exactly the gate `publish.yml` runs (pub get, analyze, format, 297 tests) plus a `pub publish --dry-run`, whose only warning was these uncommitted files. The suite was also re-run with the local path override removed so it resolved the PUBLISHED magic 0.0.6 that a real consumer gets.
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
1 participant
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.
What
Releases the socket-driven notification state from #12.
version: 0.0.3, the[Unreleased]CHANGELOG section closed as[0.0.3] - 2026-08-19, and the README install snippet moved to^0.0.3.The dependency floor
magic: ^0.0.5->^0.0.6, forEcho.connection. That accessor is what lets the realtime path tell an open connection from a closed one; without it magic's Reverb driver opens a SECOND WebSocket on a redundantconnect()rather than refusing. A0.0.zcaret pins the patch digit, so^0.0.5resolved exactly 0.0.5, which has no such accessor.This does not break the existing consumers, and does not reach them either
magic_starterandmagic_exampleboth requiremagic_notifications: ^0.0.2, which under the same0.0.zrule means<0.0.3. They keep resolving 0.0.2 and are untouched by this release. Adopting the feature in either is a bump in that repository, which drags its own release train, so it is deliberately not part of this PR.uptizmneeds nothing: it consumes this package by path, locally and in CI (the Flutter job clones the siblings).Also
Two version pins that were stale before this release: the README snippet said 0.0.2, and
CLAUDE.md's header still said 0.0.1 while the package was on 0.0.2.Verification
Exactly the gate
publish.ymlruns, in its order:flutter pub get,flutter analyze --no-fatal-infos,dart format --set-exit-if-changed,flutter test(297 pass). Plusflutter pub publish --dry-run, whose only warning was the then-uncommitted files; the four hints are the gitignoredpubspec_overrides.yaml, which does not exist in CI.The suite was also re-run with that override removed, so it resolved the published magic 0.0.6 a real consumer gets rather than the local sibling checkout.
Once merged, tag
0.0.3on master to triggerpublish.yml.