You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
server.json, the manifest that lists this package on the official MCP registry. The ecosystem was absent from every MCP directory while three competing Flutter MCP servers were listed, so an agent looking for a Flutter E2E driver found them and not this one. The entry carries repository and websiteUrl and deliberately no packages block: registryType documents npm, pypi, oci, nuget and mcpb with no pub equivalent, and both packages and remotes are optional on ServerDetail, which requires only name, description and version. Nothing in the package reads the file and no workflow publishes it, so test/server_json_version_test.dart guards the version against pubspec.yaml, along with the schema's 100 character description cap. Excluded from the pub archive for the same reason codecov.yml is. (server.json, .pubignore, test/server_json_version_test.dart)
Changed
The fluttersdk_artisan floor moves ^0.0.10 to ^0.0.16. dusk is a plugin on artisan, and 0.0.16 is where a plugin injection that matches nothing stops reporting Success over a file it never touched. The old range admitted 0.0.16 already, so nothing resolves differently on a fresh pub get; what changes is that a consumer reading the floor sees the release this package is verified against. The requirements tables in doc/getting-started/installation.md and doc/getting-started/index.md still said ^0.0.8, which a reader following them would have pinned alongside fluttersdk_dusk: ^0.0.14 two lines below and hit a resolution failure. (pubspec.yaml, doc/getting-started/installation.md, doc/getting-started/index.md, CLAUDE.md)