Skip to content

chore(deps): bump fluttersdk_artisan from 0.0.5 to 0.0.6 in /example#24

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/pub/example/fluttersdk_artisan-0.0.6
Open

chore(deps): bump fluttersdk_artisan from 0.0.5 to 0.0.6 in /example#24
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/pub/example/fluttersdk_artisan-0.0.6

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Jun 3, 2026

Bumps fluttersdk_artisan from 0.0.5 to 0.0.6.

Release notes

Sourced from fluttersdk_artisan's releases.

0.0.6

Added

  • mcp:install --invocation=<exec> option for plugin-aware .mcp.json fallback when bin/fsa is absent (writes dart run <exec> mcp:serve). Whitespace-only values are trimmed and treated as not provided, so --invocation=" " falls back to the :dispatcher shape rather than producing an invalid dart run mcp:serve entry. Plugin wrappers (fluttersdk_dusk, fluttersdk_telescope) can now inject --invocation=<plugin> automatically so substrate-only consumers without bin/fsa get the correct MCP wiring.
  • skills/fluttersdk-artisan/SKILL.md Section 8 (Community: star + issue, optional, once per session) plus a new skills/fluttersdk-artisan/references/community.md (156 lines). Trigger split: star fires after a task verified end-to-end against the running app or a clean make:* / plugin:install / mcp:install flow; issue fires only on a genuine artisan-side defect (malformed artisan_* JSON, substrate-allowlist registration failure, .mcp.json precedence broken, artisan_tinker crash on a valid expression, AOT staleness regression, hot-reload semantics inverted). Section 5 substrings (No Flutter app detected, Pipe missing, Expression compilation error, Isolate sentinel, mkfifo failed (Windows ...), etc.) are explicitly excluded from the issue trigger because they are state / environment / expression-shape signals, not bugs. Both CTAs are prose-permission, never auto-executed, gated on command -v gh && gh auth status, URL-only fallback when gh is missing, and capped at one shot per session. gh issue create uses --label bug alone; the agent-reported label is not provisioned on the artisan repo yet, so the example deliberately omits it to avoid pre-creating labels on the user's account.

Changed

  • mcp:install now writes .mcp.json atomically via the .tmp + rename pattern (mirrors StateFile.write and PluginsRegistryFile.write), so concurrent MCP clients (Claude Code, Cursor, Windsurf) never observe a half-written file when the command is interrupted mid-write.
  • Repo flow: adopted GitHub Flow (single long-lived master; retired the develop accumulator and all merged feature branches). CLAUDE.md now carries this as Golden Rule 7 plus a ## Branching section documenting task-branch naming (<type>/<kebab-case-topic>), the squash-vs-rebase-vs-merge decision, the release shape (release/X.Y.Z PR bumps pubspec + promotes CHANGELOG, then tag fires .github/workflows/publish.yml), and the external-contributor fork-and-PR shape. delete_branch_on_merge: true enabled on origin so merged branches auto-cleanup.

Fixed

  • artisan_tinker MCP tool description and the eval input-schema example expression scrubbed of consumer-specific class names (MonitorController.instance.refresh(), User.current.name). Replaced with framework-neutral examples (WidgetsBinding.instance.lifecycleState, MyService.instance.refresh()) and tightened the scope language ("controllers, models, framework facades" -> "top-level functions, singletons, services"). Surfaces to every MCP client (Claude Code, Cursor, Windsurf, etc.) on tools/list, so the published 0.0.x docs no longer leak private consumer-app identifiers.
  • MCP serverInfo.version no longer drifts (continued from 0.0.5 NIT 7): the hardcoded version: '0.0.5' literal in lib/src/mcp/mcp_server.dart is manually synced to '0.0.6' as part of this release-cut commit. A future patch may switch to a build-time constant to eliminate manual drift recurrence (still deferred per scope).
Changelog

Sourced from fluttersdk_artisan's changelog.

[0.0.6] - 2026-05-28

Added

  • mcp:install --invocation=<exec> option for plugin-aware .mcp.json fallback when bin/fsa is absent (writes dart run <exec> mcp:serve). Whitespace-only values are trimmed and treated as not provided, so --invocation=" " falls back to the :dispatcher shape rather than producing an invalid dart run mcp:serve entry. Plugin wrappers (fluttersdk_dusk, fluttersdk_telescope) can now inject --invocation=<plugin> automatically so substrate-only consumers without bin/fsa get the correct MCP wiring.
  • skills/fluttersdk-artisan/SKILL.md Section 8 (Community: star + issue, optional, once per session) plus a new skills/fluttersdk-artisan/references/community.md (156 lines). Trigger split: star fires after a task verified end-to-end against the running app or a clean make:* / plugin:install / mcp:install flow; issue fires only on a genuine artisan-side defect (malformed artisan_* JSON, substrate-allowlist registration failure, .mcp.json precedence broken, artisan_tinker crash on a valid expression, AOT staleness regression, hot-reload semantics inverted). Section 5 substrings (No Flutter app detected, Pipe missing, Expression compilation error, Isolate sentinel, mkfifo failed (Windows ...), etc.) are explicitly excluded from the issue trigger because they are state / environment / expression-shape signals, not bugs. Both CTAs are prose-permission, never auto-executed, gated on command -v gh && gh auth status, URL-only fallback when gh is missing, and capped at one shot per session. gh issue create uses --label bug alone; the agent-reported label is not provisioned on the artisan repo yet, so the example deliberately omits it to avoid pre-creating labels on the user's account.

Changed

  • mcp:install now writes .mcp.json atomically via the .tmp + rename pattern (mirrors StateFile.write and PluginsRegistryFile.write), so concurrent MCP clients (Claude Code, Cursor, Windsurf) never observe a half-written file when the command is interrupted mid-write.
  • Repo flow: adopted GitHub Flow (single long-lived master; retired the develop accumulator and all merged feature branches). CLAUDE.md now carries this as Golden Rule 7 plus a ## Branching section documenting task-branch naming (<type>/<kebab-case-topic>), the squash-vs-rebase-vs-merge decision, the release shape (release/X.Y.Z PR bumps pubspec + promotes CHANGELOG, then tag fires .github/workflows/publish.yml), and the external-contributor fork-and-PR shape. delete_branch_on_merge: true enabled on origin so merged branches auto-cleanup.

Fixed

  • artisan_tinker MCP tool description and the eval input-schema example expression scrubbed of consumer-specific class names (MonitorController.instance.refresh(), User.current.name). Replaced with framework-neutral examples (WidgetsBinding.instance.lifecycleState, MyService.instance.refresh()) and tightened the scope language ("controllers, models, framework facades" -> "top-level functions, singletons, services"). Surfaces to every MCP client (Claude Code, Cursor, Windsurf, etc.) on tools/list, so the published 0.0.x docs no longer leak private consumer-app identifiers.
  • MCP serverInfo.version no longer drifts (continued from 0.0.5 NIT 7): the hardcoded version: '0.0.5' literal in lib/src/mcp/mcp_server.dart is manually synced to '0.0.6' as part of this release-cut commit. A future patch may switch to a build-time constant to eliminate manual drift recurrence (still deferred per scope).
Commits
  • 06c5f11 release: 0.0.6 (mcp:install --invocation + artisan_tinker scrub + community CTA)
  • ed81b6b docs(claude): adopt GitHub Flow as Golden Rule 7 + Branching section (#20)
  • 9c1f857 feat(mcp): add mcp:install --invocation=<exec> option for plugin-aware .mcp.j...
  • 52e3e9a chore(deps): bump softprops/action-gh-release from 2 to 3 (#11)
  • 108edd8 chore(deps): bump fluttersdk_artisan from 0.0.4 to 0.0.5 in /example (#12)
  • acf1acb Merge pull request #17 from fluttersdk/fix/tibdex-app-token
  • 2a4602e style(dispatch): align tibdex with-block indent (+2 spaces)
  • bd2f02c fix(dispatch): switch to tibdex/github-app-token@v2.1.0
  • 9d6b831 Merge pull request #16 from fluttersdk/fix/pin-create-github-app-token
  • bc8244d fix(dispatch): pin create-github-app-token to v3.1.1
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [fluttersdk_artisan](https://github.com/fluttersdk/artisan) from 0.0.5 to 0.0.6.
- [Release notes](https://github.com/fluttersdk/artisan/releases)
- [Changelog](https://github.com/fluttersdk/artisan/blob/master/CHANGELOG.md)
- [Commits](0.0.5...0.0.6)

---
updated-dependencies:
- dependency-name: fluttersdk_artisan
  dependency-version: 0.0.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Jun 3, 2026

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants