chore(release): 0.3.0

[anilcancakir]

Prepares 0.3.0 for publish. The version was cut on 2026-09-09 and never tagged; three commits landed after it (#28, #29, #30) and wrote into a fresh [Unreleased] above a release that had not gone out.

Tagging as it stood would have published code whose own changelog calls part of it unreleased, because publish.yml builds the GitHub release from the tag and the CHANGELOG section behind it. So the section is folded rather than left split, and dated for the day it ships. Nothing else moves: pubspec.yaml, CLAUDE.md, README.md and doc/getting-started/installation.md have said 0.3.0 since the version was cut, and magic/skills/magic-framework/references/plugin-notifications.md is already stamped v0.3.0.

What 0.3.0 now carries

• The cold-start click held until something listens (Hold a cold-start click until something listens, and cut 0.3.0 #27), the bulk channel row on the preferences screen, and the bell header fix, all as cut.
• notifications:doctor reading the APNs environment each build configuration signs against (Check the APNs environment each build configuration signs against #28), plus the flavoured-project fix that check needed (Read the APNs environment of a flavoured project #29): Release-production and its siblings dropped out of the map entirely, so the check printed a clean bill of health for exactly the shape it exists to catch.
• The documentation pass on what happens when somebody taps a push (Say what happens when somebody taps a push #30), including the toOneSignal example that sent a destination the app could not read.

Gates

Run with pubspec_overrides.yaml moved aside, so the resolution is the one the publish workflow sees: magic 0.0.11, fluttersdk_wind 1.5.3, fluttersdk_artisan 0.0.14, all hosted.

• flutter test: 644 passed
• dart analyze: no issues
• dart format --output=none --set-exit-if-changed .: 0 of 99 changed
• dart pub publish --dry-run: one warning, the uncommitted CHANGELOG at the time it ran. Nothing else.

After this merges

git tag 0.3.0 && git push origin 0.3.0. This release is what unblocks magic_starter 0.0.27, whose floor moves to ^0.3.0 (fluttersdk/magic_starter#129): that PR's Published graph job is red until this is on pub.dev.

Author: Anılcan Çakır anilcan.cakir@gmail.com

[kodizm]

Note

Kodizm (AI-generated). May contain mistakes; verify before acting.

Changelog-only release fold; the move is correct and every version string in the repo already agrees with it.

The diff is exactly two lines: the ## [0.3.0] heading moves above the ### Documentation block and its date changes from 2026-09-09 to 2026-09-12. No entry text is added, removed or reordered, so the three post-cut commits (#28, #29, #30) end up inside the release that ships them and [Unreleased] is left empty, which is what a tag built from this section should read.

Verified rather than taken on trust:

• pubspec.yaml:3, CLAUDE.md:5, README.md:72, doc/getting-started/installation.md:30 and lib/src/cli/notifications_artisan_provider.dart:19 all already say 0.3.0, so nothing else needed to move with this.
• The file carries no [0.3.0]: … link reference definitions at the bottom, so retitling the heading breaks no link.
• git log shows 6c06022 (Say what happens when somebody taps a push #30), ceef4c4 (Read the APNs environment of a flavoured project #29) and fecd076 (Check the APNs environment each build configuration signs against #28) landing after e982245, which cut the version - the commits being folded are the ones the fold claims.

Minor

CHANGELOG.md:7-51 — the 0.3.0 section now has three ### Fixed blocks and two ### Added blocks interleaved (lines 16, 21, 25, 30, 51), because the fold stacked the post-cut subsections on top of the pre-cut ones rather than merging like with like. Keep-a-Changelog expects one subsection per type per release, and a reader scanning the published release notes for what was fixed has to find three separate lists. Purely cosmetic, and merging them would make the diff larger than the one-line move it currently is, so this is a judgement call rather than a defect. (maintainability)

Tests

Nothing to test - no Dart source, config or asset changed. The gate numbers quoted in the description (644 tests, clean analyze, clean format) belong to the commits already merged, not to this diff.

Checks I ran

• kodizm.read_pull_request_diff (manifest and patch): 1 file, CHANGELOG.md, +2/-2, scope: full, nothing dropped or diff-less.
• grep -rn "0\.3\.0" across md/yaml/dart: five call sites, all already 0.3.0.
• grep -n "^## \|^### " CHANGELOG.md: confirms the heading layout above, exit=0.
• git log --oneline -8: confirms which commits landed after the version was cut.
• No test or analyzer run, deliberately: the change touches no code they could exercise.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!