release: fluttersdk_artisan 0.0.11 - #44
Merged
Merged
Conversation
Ships the session-key fix from #43: the isolation 0.0.10 introduced only held for callers standing in the repo root, and a command run from a package subdirectory got a false refusal on exactly the layout the ownership guard was written to permit. All six stamps bumped in one pass this time, using the list the 0.0.10 cut had to discover: pubspec, the MCP handshake string, both example pubspecs, the skill stamp, and the example lockfile. The two example pubspecs moved together, so `flutter pub get` resolved without the `version solving failed` that caught the last cut, and the MCP guard test confirms the handshake string moved with the package.
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
1 participant
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.
What
Patch release for #43.
The session isolation 0.0.10 introduced only held for callers standing in the repo root.
sessionOwnershipErrorlets a command run from a package subdirectory through, butsessionPathForhashed the working directory, so from there the session lookup missed, fell back to the shared pointer, and with two apps up got refused for driving somebody else's app. That is a false refusal on exactly the layout the guard was written to permit, and it is live in 0.0.10.Stamps
All six bumped in one pass, using the list the 0.0.10 cut had to discover the hard way:
pubspec.yamllib/src/mcp/mcp_server.dartmcp_server_version_test.dartexample/pubspec.yamlexample/packages/awesome_plugin/pubspec.yamlskills/fluttersdk-artisan/SKILL.mdexample/pubspec.lockBoth example pubspecs moved together, so
flutter pub getresolved cleanly rather than failing withversion solving failedthe way the 0.0.10 attempt did. The MCP guard test passes, confirming the handshake string moved with the package.Testing
dart formatzero diff,dart analyzezero issues, 1222 tests green,dart pub publish --dry-runclean.After merge
git tag 0.0.11 && git push origin 0.0.11.