Skip to content

v0.3.56 — Compile results use current evidence

Choose a tag to compare

@FoxsterDev FoxsterDev released this 23 Aug 15:34
· 53 commits to master since this release

Why this matters

Unity can keep old compiler messages in memory while a newer compile has a different structural problem. Showing the old message first can send a developer to the wrong file and make a stale failure look current.

What this gives you

  • Refresh, compile, and direct-test results now promote assembly-definition problems from the current editor-log generation.
  • Duplicate references, missing references, invalid asmdef files, and rejected assemblies get a specific assembly_definition_error classification.
  • The compact response keeps the important current error and gives a safe recovery action.
  • If the log anchor cannot be trusted, the fallback refuses to claim current truth instead of reusing a previous session’s error.

Validation

  • Current-generation log promotion and stale-anchor refusal are covered by focused host regression tests.