deps(python): bump graphifyy from 0.9.30 to 0.9.31 in the python-minor-and-patch group

[dependabot]

Bumps the python-minor-and-patch group with 1 update: graphifyy.

Updates graphifyy from 0.9.30 to 0.9.31

Release notes

Sourced from graphifyy's releases.

v0.9.31

Resolution-accuracy fixes, an MCP SDK compatibility widening, and community extractor fixes.

MCP

• The MCP server is now dual-compatible with the mcp SDK 1.x and 2.x, lifting the mcp<2 cap from 0.9.30 to mcp>=1,<3 (#2308, thanks @​NiSHoW). _build_server binds the same handlers via the 1.x decorator API or the 2.x on_* constructor callbacks at runtime, and adapts Tool.inputSchema, Resource.uri, and the dropped AnyUrl re-export. Verified with full stdio handshakes under mcp 1.29 and 2.0.

Resolution / graph accuracy

• C# member calls on a typed receiver no longer drop true calls edges when the same local name is reused across methods (#2299, thanks @​JensD-git). Receiver typing is now per-method (mirroring the Java resolver) instead of per-file, so an untypable var x = ... in one method can't delete a typed-parameter call edge in another.
• SQL cross-file table references (e.g. a prisma migration referencing a table created in an earlier one) resolve to the real table node instead of leaking an absolute-path id and losing the foreign key (#2324). References mint a sourceless stub that collapses onto the real definition, and identifiers are normalized so "public"."users" matches public.users.
• graphify path and explain no longer print reversed hops (#2309): they recover edge direction from the stored _src/_tgt markers instead of the persisted endpoint order.
• export const X = <scalar> now emits a graph node, so a named import of a scalar export is no longer left dangling (#2266, thanks @​oleksii-tumanov).
• Go predeclared functions (make, len, append, ...) no longer fabricate call edges to same-named user symbols (#2313, thanks @​PathGao); the filter is scoped to Go bare-identifier callees.
• graphify explain refuses and lists candidates when a name matches symbols in more than one file, instead of silently resolving to an arbitrary one (#2233, thanks @​0bLoM).

Install

• The Antigravity install workflow no longer hardcodes the global skill path for a project-scoped install (#2319, thanks @​MalikHaroonKhokhar).

Changelog

Sourced from graphifyy's changelog.

0.9.31 (2026-07-30)

• Feature: the MCP server is dual-compatible with SDK 1.x AND 2.x (#2308, thanks @​NiSHoW), lifting the mcp<2 cap 0.9.30 introduced to mcp>=1,<3. The 2.0 SDK removed the low-level decorator API (Server.list_tools/call_tool/...); _build_server now binds the same handlers via the 1.x decorators or the 2.x on_* constructor callbacks, picked at runtime, and adapts Tool.inputSchema, Resource.uri (plain str in 2.x), and the dropped AnyUrl re-export. Verified with full stdio handshakes under both mcp 1.29 and 2.0.
• Fix: C# member calls on a typed receiver no longer drop true calls edges when the same local name is reused across methods (#2299, thanks @​JensD-git). Receiver typing was per-file and poisoned a name on any conflicting/untypable rebind anywhere in the file; it is now per-method (mirroring the Java resolver), so an untypable var x = ... in one method can't delete a typed-parameter call edge in another.
• Fix: SQL cross-file table references (e.g. a prisma migration referencing a table created in an earlier one) resolve to the real table node instead of leaking an absolute-path id and losing the foreign key (#2324). References now mint a sourceless stub that collapses onto the real definition, and identifiers are normalized so a quoted definition ("public"."users") matches an unquoted reference (public.users).
• Fix: graphify path and explain no longer print reversed hops (#2309). They now recover edge direction from the stored _src/_tgt markers instead of the persisted endpoint order, so a graph.json written with flipped storage order (older graphs, raw dumps, merge-driver output) renders the true direction.
• Fix: export const X = <scalar> now emits a graph node, so a named import of a scalar export is no longer left dangling (#2266, thanks @​oleksii-tumanov).
• Fix: Go predeclared functions (make, len, append, new, ...) no longer fabricate call edges to same-named user symbols (#2313, thanks @​PathGao); the filter is scoped to Go bare-identifier callees so it can't affect other languages or same-file method calls.
• Fix: graphify explain refuses and lists candidates when a name matches symbols in more than one file, instead of silently resolving to an arbitrary one (#2233, thanks @​0bLoM).
• Fix: the Antigravity install workflow no longer hardcodes the global skill path for a project-scoped install (#2319, thanks @​MalikHaroonKhokhar).

Commits

• 4fe1109 chore(release): 0.9.31
• 5d1d103 chore: bump to 0.9.31; changelog for #2308/#2299/#2324/#2309/#2266/#2313/#223...
• 50be9dc fix(cli): recover edge direction from _src/_tgt in path and explain (#2309)
• c8163d8 fix(sql): sourceless stubs + identifier normalization for cross-file table re...
• f99f8d7 fix(csharp): per-method receiver typing so cross-method name reuse stops drop...
• 2ca565a fix: explain no longer resolves an ambiguous name to an arbitrary file
• 3868434 fix(go): scope the predeclared-function filter to Go bare identifiers
• 773250a fix(go): filter Go predeclared functions from call-target resolution
• d7cb5b1 fix(extract): emit nodes for exported scalar bindings
• bdf62ce fix(install): stop hardcoding the global skill path in the Antigravity workfl...
• Additional commits viewable in compare view

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions