Typst's creator explains why releasing version 1.0 is not yet appropriate despite the tool being production-ready. The core challenge is defining what constitutes a breaking change and how to handle ecosystem disruption when changes are made. Two proposed solutions are outlined: a 'target' version mechanism in typst.toml that lets packages declare which Typst version's behavior they expect (similar to Rust editions but time-limited), and automated migration tooling for syntactic and semantic breaking changes. The target mechanism would give packages time to adapt without immediately breaking the ecosystem, while migration tooling would help users update their documents. Upcoming potential breaking changes include math precedence rules and function parameter syntax changes.
