Bump sem-core from 0.10.1 to 0.13.0

[dependabot]

Bumps sem-core from 0.10.1 to 0.13.0.

Changelog

Sourced from sem-core's changelog.

[0.13.0] - 2026-06-16

Fixed

• Kotlin: resolve method calls through typed receivers that the tree-sitter-kotlin-ng grammar exposes positionally (no name/type fields). Several scope-resolution paths used field names from the older grammar and silently produced no call edges. Fixed: typed function parameters (fun f(s: Scenario) { s.method() }); class field types from property declarations (val conn: Connection) and primary-constructor properties (class Tx(val conn: Connection)); chained field access (val s = container.scenario; s.method()); and declared/inferred return types, so val c = get(); c.method() resolves. sem context/impact/log now find these Kotlin callers. Thanks @​mrsirrisrm.
• Java: name field entities by their declarator instead of their type. private FooService fooService; was extracted as an entity named FooService (its type) rather than fooService, because field_declaration has no name field and the generic fallback returned the first type identifier. This also collided class and field names in the symbol table. sem entities/diff/log now report the correct field name. Thanks @​mrsirrisrm.
• Java: resolve cross-file receiver.method() call edges. Local variable types weren't recorded (Dog d = new Dog() and object_creation_expression RHS were ignored), class field types weren't tracked, and ClassName.staticMethod() calls were dropped, so sem impact/context reported few or no cross-file dependents on Java, a false negative that read as "safe to change." The Spring field-injection pattern (@Inject private FooService foo; ... foo.bar()) now resolves. Thanks @​mrsirrisrm.
• On Windows, the MCP tools sem_impact, sem_context, and sem_log never resolved an entity: resolve_file_path returned OS-native (backslash) relative paths while graph entities store forward-slash file_paths, so the (name, file_path) match always failed. Relative paths are now emitted with forward slashes on all platforms. Thanks @​Turntwo.

[0.12.0] - 2026-06-15

Added

• While the spinner is up, sem shows a rotating one-line tip about another useful command underneath it, like the hints under Claude Code's spinner. sem diff (the most-used command) now shows the spinner during its compute, so you learn about sem impact, sem context, sem blame, the MCP server, etc. while you wait. Strictly stderr and TTY-only, so it never touches output, pipes, JSON, or agent sessions, and disappears when the work finishes. Disable with SEM_NO_PROGRESS=1.
• After a slow local build (3s+) when you're logged out, sem prints one dim line with the time you just spent and notes that sem cloud serves the same graph warm in milliseconds. Throttled to once a day, TTY-only, and uses your real elapsed time (no inflated claims). Disable with SEM_NO_PROGRESS=1.
• The MCP server (sem mcp) now keeps its in-memory entity graph live with a background file watcher. Previously sem_impact and sem_context re-walked and re-stat'd the entire repo on every call just to check whether the cached graph was still fresh, which on a large repo is real per-call overhead. A watcher now tracks filesystem changes, so calls where nothing changed return the cached graph instantly (no walk, no stat), and an edit triggers an incremental rebuild of only the changed files. Your uncommitted edits are reflected without restarting the server. Disable with SEM_NO_WATCH=1.

Changed

• Graph resolution now uses faster hash collections in hot paths to reduce graph build overhead.
• Scope resolution caches repeated reference lookups during graph builds to reduce redundant resolver work.
• Graph builds avoid retaining import scan source text after import extraction, reducing peak memory use.
• sem context now prints the full source of the target entity in the terminal. It previously showed only the first line, so reading a function meant falling back to --json. Related entities still show a one-line signature so the context map stays scannable.
• sem context and sem impact (CLI and the sem_context / sem_impact MCP tools) now accept Class.method (and Outer.Inner.method) to address a method by name, not only the bare method name or a full entity id.

Fixed

• Fixed: super::module::func() calls were dropped from the entity graph, so impact and context under-reported the blast radius across modules. Multi-segment Rust path-prefixed calls (super::/crate::/self::) now resolve to the real entity.

[0.11.1] - 2026-06-14

Added

• sem impact now shows the uv-style progress spinner during the cold graph build (it's the most-used graph command). Same stderr/TTY gating as graph and context.

[0.11.0] - 2026-06-14

Added

• Progress spinner for slow graph builds. sem graph and sem context now show a uv-style spinner and a summary line (e.g. 135,298 entities, 7,743 files in 6.6s) while building the entity graph. Strictly stderr and TTY-only, so pipes, JSON, and agent/MCP sessions are unaffected. Disable with SEM_NO_PROGRESS=1.

• SQL support (.sql, .psql, .pgsql, .ddl) via the official DerekStride/tree-sitter-sql grammar. Extracts tables, views, materialized views, functions, indexes, types, schemas, triggers, sequences, and databases. Thanks @​robahtou for the request (#339).

• Start tracking project changes in CHANGELOG.md.

• Add a pull request check that asks contributors to include a changelog entry.

• sem entities accepts multiple file or directory path arguments.

Changed

• Sparse checkouts now work. libgit2 cannot read a sparse index (unsupported mandatory extension: 'sdir') and its workdir diff reported sparse-excluded files as deleted; sem now routes working and staged diffs through the git CLI when a sparse checkout is detected. Thanks for the report (#330).

... (truncated)

Commits

• 9d46dc3 Release 0.13.0 (minor: pub InitStrategy gained a variant)
• 7101513 Release 0.12.1
• b4504ea Merge PR #367: fix MCP entity resolution on Windows
• 6cd25bf Merge PR #360: Java cross-file method-call resolution via type tracking
• cf0b7df Merge PR #361: name Java field entities by declarator, not type
• ca168aa Merge PR #359: Kotlin call resolution for tree-sitter-kotlin-ng
• 9fb9f69 Fix MCP entity resolution on Windows
• d088481 Release 0.12.0
• 4443e7a cli: nudge logged-out users toward sem cloud at the moment of pain
• 3978a9b cli: rotating command tips under the spinner
• 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 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)

[inspect-review]

inspect review

Triage: 6 entities analyzed | 0 critical, 0 high, 6 medium, 0 low
Verdict: standard_review

Findings (0)

---

Reviewed by inspect | Entity-level triage found 0 high-risk changes