chore(release): 1.0.0-alpha.4#10
Merged
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Release housekeeping PR to publish magic as 1.0.0-alpha.4, aligning package metadata and release notes for the new pre-release.
Changes:
- Bump package version to
1.0.0-alpha.4inpubspec.yaml. - Update
CLAUDE.mdversion header to1.0.0-alpha.4. - Finalize
CHANGELOG.mdwith a new1.0.0-alpha.4section and release date.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| pubspec.yaml | Updates package version for the 1.0.0-alpha.4 release. |
| CLAUDE.md | Syncs documented framework version with the release. |
| CHANGELOG.md | Adds the 1.0.0-alpha.4 release entry and date. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
anilcancakir
added a commit
that referenced
this pull request
Jun 25, 2026
… step Wires magic_devtools, fluttersdk_dusk, and fluttersdk_telescope (deps plus kDebugMode main.dart integration) in a single install step instead of the manual multi-step setup. The wiring is idempotent and the no-flag install path is unchanged (#10).
anilcancakir
added a commit
that referenced
this pull request
Jun 25, 2026
…100) * feat: add magic:install --with-devtools to wire the debug trio in one step Wires magic_devtools, fluttersdk_dusk, and fluttersdk_telescope (deps plus kDebugMode main.dart integration) in a single install step instead of the manual multi-step setup. The wiring is idempotent and the no-flag install path is unchanged (#10). * fix(cli): keep --with-devtools main.dart import ordering directives_ordering-clean buildDevtoolsWiring injected the debug-trio package imports immediately before `void main(`, landing them after the relative `config/...` imports the install stub emits. That violates directives_ordering (package imports must precede relative imports, and foundation must precede material), so a freshly installed --with-devtools app surfaced analyzer warnings. Anchor each injected package import against the existing package import it must sit beside: foundation before flutter/material, fluttersdk_* before magic, magic_devtools/* after magic and before the first relative import (falling back to the void main( anchor when no relative import is present). The kDebugMode block injection is unchanged and the transform stays idempotent. Verified the generated import block is directives_ordering-clean via the analyzer. Addresses Copilot review comment on PR #100.
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.
Summary
1.0.0-alpha.4Changelog
🔧 Improvements
Test plan
dart analyze— zero issuesdart format— zero changesdart pub publish --dry-run— clean (only uncommitted warning pre-commit)