Repository navigation
release: 0.0.20 - #68
Merged
Merged
Conversation
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.
Patch. Releases #67, the only change since 0.0.19.
What ships
ExtensionNotRegisteredExceptionandArtisanCommand.exitTryAgain(75).VmServiceClient.callServiceExtensionmaps JSON-RPC-32601to the new exception on the first call and on both retries, so a connected command can tell "not registered yet" from a failed call without importingpackage:vm_service. The dispatcher prints it as one line and exits 75 (EX_TEMPFAIL).starton a cold native build no longer exits on a stack fragment. When the scrape times out andflutter runis still alive,startkeeps the booting session, prints thestatus/ retry /--timeouthints and exits 75; when it is gone, it reaps the session, names the log and exits 1. A connected command against a booting session whoseflutter runis alive also exits 75 (was 1).No sibling inside the org calls
-32601or catchesvm.RPCErrorfromcallServiceExtension(grepped dusk, telescope, magic, magic_devtools, magic_cli, magic_example, magic_starter; the one hit is dusk's CDP client, which does not go through this path), so the new exception type changes nothing for them. Their^0.0.19constraints already admit 0.0.20.Stamps
pubspec.yamllib/src/mcp/mcp_server.dart(handshake, test-guarded)server.json(test-guarded)example/pubspec.yaml,example/packages/awesome_plugin/pubspec.yamlexample/pubspec.lock/Users/path)skills/fluttersdk-artisan/SKILL.mdbody stampskills/fluttersdk-artisan/SKILL.mdfrontmatterversion:SKILL.md,mcp-tools.mdandstate-and-recovery.md)doc/commands/install.md(x3),doc/getting-started/installation.md(x2),doc/plugins/authoring.md^0.0.19^0.0.20CLAUDE.mdrelease linegit grep -nF 0.0.19 -- ':!CHANGELOG.md' ':!*.lock'is empty. artisan pins no fluttersdk sibling, so there are no floors to move.Gates
dart format --output=none --set-exit-if-changed lib/ test/ bin/: 197 files, 0 changed.dart analyze lib test bin: no issues.dart test --exclude-tags=integration --timeout=30s: +1427, all passed.dart pub publish --dry-run: 0 warnings, from the commit.Tag