Context
Magic finalized its pub.dev consumption hat in commit 618f454 (fluttersdk/magic@618f454):
# references/magic/pubspec.yaml
dependencies:
fluttersdk_artisan: ^0.0.5 # was: ^1.0.0-alpha.1
The published fluttersdk_artisan on pub.dev is on the 0.0.x version line (current: 0.0.5); the ^1.0.0-alpha.1 constraint historically pointed at a pre-publish staging hat and never matched a real pub.dev release.
This sibling package still declares the old constraint:
# THIS_REPO/pubspec.yaml (current)
dependencies:
fluttersdk_artisan: ^1.0.0-alpha.1 # ← does not match any pub.dev version
Impact
Consumers (uptizm-app discovered this) that depend on both magic and this sibling via path/git refs hit a pub resolution failure:
Because every version of <THIS_PACKAGE> from path depends on
fluttersdk_artisan ^1.0.0-alpha.1 and app depends on fluttersdk_artisan ^0.0.5,
<THIS_PACKAGE> from path is forbidden.
The current workaround in uptizm-app is dependency_overrides: fluttersdk_artisan: ^0.0.5 — fine for one consumer, but every downstream that wants to consume both magic + this sibling needs the same override until this repo bumps.
Ask
Bump fluttersdk_artisan constraint in pubspec.yaml from ^1.0.0-alpha.1 to ^0.0.5. Run flutter pub get, then flutter analyze + flutter test to verify API compatibility (the artisan API surface in 0.0.x is the same one this sibling already targets at runtime; only the constraint string is wrong).
This is a mechanical 1-line pubspec edit + verification.
Related
- magic commit aligning to pub.dev artisan: fluttersdk/magic@618f454
- magic CHANGELOG
[Unreleased] Plan 1 entry referencing the alignment.
Filed by LLM agent (Claude Code) acting on behalf of @anilcancakir during magic/uptizm-app pub.dev alignment work.
Context
Magic finalized its pub.dev consumption hat in commit
618f454(fluttersdk/magic@618f454):The published
fluttersdk_artisanon pub.dev is on the0.0.xversion line (current:0.0.5); the^1.0.0-alpha.1constraint historically pointed at a pre-publish staging hat and never matched a real pub.dev release.This sibling package still declares the old constraint:
Impact
Consumers (uptizm-app discovered this) that depend on both
magicand this sibling via path/git refs hit a pub resolution failure:The current workaround in uptizm-app is
dependency_overrides: fluttersdk_artisan: ^0.0.5— fine for one consumer, but every downstream that wants to consume both magic + this sibling needs the same override until this repo bumps.Ask
Bump
fluttersdk_artisanconstraint inpubspec.yamlfrom^1.0.0-alpha.1to^0.0.5. Runflutter pub get, thenflutter analyze+flutter testto verify API compatibility (the artisan API surface in0.0.xis the same one this sibling already targets at runtime; only the constraint string is wrong).This is a mechanical 1-line pubspec edit + verification.
Related
[Unreleased]Plan 1 entry referencing the alignment.Filed by LLM agent (Claude Code) acting on behalf of @anilcancakir during magic/uptizm-app pub.dev alignment work.