chore(release): 0.0.11

[anilcancakir]

Cuts 0.0.11. One entry, promoted unchanged from [Unreleased]: plugin-starter.md following magic_starter off the alpha rail (#155).

Why a release for a documentation change. skills/magic-framework/references/plugin-starter.md is the only agent-facing document magic_starter has, since its .pubignore keeps CLAUDE.md and .claude/ out of the published archive, and it is versioned by THIS repository's releases. The mirror to fluttersdk/ai rides publish.yml's registry job rather than the push, so without a release the registry keeps describing magic_starter as an alpha-rail package while 0.0.27 goes out.

No lib/ change, so no API surface moves and SKILL.md's own version: stays at 0.1.17; only its body stamp follows the package version.

The four stamps

File	Change
pubspec.yaml	0.0.10 to 0.0.11
CHANGELOG.md	## [Unreleased] to ## [0.0.11] - 2026-09-12, fresh [Unreleased] above
skills/magic-framework/SKILL.md	body stamp magic 0.0.10 to magic 0.0.11
example/pubspec.yaml	the version: beside path: .. to 0.0.11

Gates

Run twice: once against the sibling working trees, then with pubspec_overrides.yaml moved aside so the resolution is the one the publish workflow sees (fluttersdk_wind 1.5.3, fluttersdk_artisan 0.0.14, fluttersdk_wind_diagnostics_contracts 1.1.0, all hosted).

• flutter test: 1464 passed, both runs
• dart analyze: no issues
• dart format --output=none --set-exit-if-changed .: 0 of 337 changed
• dart pub publish --dry-run: 1 warning (uncommitted files at the time it ran) and the standing hint that 0.0.11 is behind the 1.0.0-alpha.13 prerelease line, which is the same note 0.0.10 carried and is consistent with master being the active 0.0.x line.

After this merges

git tag 0.0.11 && git push origin 0.0.11. Worth watching: 0.0.10's publish run failed inside the reusable workflow at dart pub get with Insufficient permissions to the resource at the https://pub.dev package repository, so the pub.dev publish, the GitHub release and the registry sync were all done by hand. wind 1.5.3 failed identically the same day on an unchanged workflow pin. This release is the retry that tells us whether the pipeline recovered.

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[kodizm]

Note

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

Release bookkeeping only - the four version stamps plus the example lockfile are consistent, and every gate the publish workflow runs is green locally, so nothing blocks the tag.

I verified the change rather than trusting the description: the diff is five files (pubspec.yaml, CHANGELOG.md, skills/magic-framework/SKILL.md, example/pubspec.yaml, example/pubspec.lock), no lib/ change, so there is no API surface to review. grep -rn "0\.0\.10" across *.md/*.yaml/*.dart/*.lock outside CHANGELOG.md returns nothing, so no stamp was left behind - including example/pubspec.lock, which is bumped in step with example/pubspec.yaml. SKILL.md's version: 0.1.17 frontmatter correctly stays put while only the body stamp follows the package version, matching the "no lib/ change" claim.

The CHANGELOG promotion is shaped the way publish.yml needs it: the github-release job runs awk "/^## \[$VERSION\]/{flag=1; next} /^## \[/{flag=0} flag", and the new ## [0.0.11] - 2026-09-12 heading with a fresh empty ## [Unreleased] above it extracts the Improvements entry cleanly and stops at ## [0.0.10].

Note that the skills/magic-framework/references/plugin-starter.md content the changelog entry describes is not in this diff - it landed in #155 and is only being promoted here. I checked its stamp in the working tree (<!-- magic_starter v0.0.27 | Updated: 2026-09-11 -->) and it matches what the entry says, but I did not re-review that file's contents.

Tests

No behaviour changes, so no new tests are expected; the existing suite passes unchanged at 1464 tests.

Checks I ran

• flutter pub get - exit 0
• dart format --output=none --set-exit-if-changed . - exit 0, 0 of 337 changed (an earlier run before pub get reported 37 changed; that was the missing package_config forcing a language-version fallback, not a real diff)
• dart analyze - exit 0, "No issues found!"
• flutter test - exit 0, "+1464: All tests passed!"
• dart pub publish --dry-run - exit 0, 0 warnings and the single standing hint that 0.0.11 is earlier than the 1.0.0-alpha.13 prerelease, which is expected on the active 0.0.x line

Ran against the checked-in resolution in this container, not with pubspec_overrides.yaml moved aside; the results match the second run reported in the description.