Lasm 0.3.1

Lasm 0.3.1

A small release after the 0.3.0 launch: the starter code is now MIT-0, and Lasm
points you to a bug report when it hits an internal error. Upgrade with
npm install -D @lasm/cli@0.3.1. Nothing changes in how programs build or run.

What's new

• Starter code under MIT No Attribution (MIT-0). Everything that lasm init
  and npm create @lasm put in a new project, templates/, examples/, and the
  code samples in the README and docs/ are now also under MIT-0. The code is
  yours to use without keeping Lasm's notice. Lasm itself stays MIT.
  • @lasm/cli carries LICENSE-MIT-0, templates/LICENSE and
    examples/LICENSE.
  • Its license field names MIT-0 next to MIT and the bundled components.
  • Built apps' THIRD_PARTY_NOTICES.txt is unchanged: it still lists Lean,
    Emscripten and the other runtime components that a build contains.
• lasm --version (also -v) prints the version, the Lean release, the
  JavaScript runtime and the platform, for example
  lasm 0.3.1 (@lasm/cli; Lean 4.35.0; Node 26.12.1; linux-x64).
• Bug reports. After an unexpected internal error, the CLI and lasm dev
  print the error's stack and then one line:
  If this looks like a Lasm bug, please report it: https://github.com/Millillion/lasm/issues/new?template=bug.yml.
  An internal error is a programming error inside Lasm, such as a TypeError or
  a failed internal assertion. Lean errors in your code, usage errors and the
  messages Lasm gives on purpose (a missing tool, an unsupported platform) never
  print it.
• Issue templates on GitHub:
  • a bug report form, which asks for lasm --version, the operating system, the
    Node/Bun/Deno version, the target, a template or project, and the output;
  • a feature request form;
  • links to the documentation and to Lean's Zulip for questions about Lean
    itself.

Fixes

• The post-release template check (published-templates.yml) now skips when the
  release run that triggered it published nothing. Before, a release run that
  only waited for the checks started it against the previous release.

Limits

Unchanged from 0.3.0: see the 0.3.0 notes.

Validation

Before release, release-checks passed for the released commit, with the same
gates as 0.3.0:

• the five-platform candidate checks;
• the edge and Bun/Deno checks;
• the browser, Lasm.UI, WASI/Fastly, fullstack, unit and dev-loop checks;
• the Lasm.JS hang stress;
• the npm rehearsal of the exact packages on five platforms, which now also
  checks that the installed CLI carries the MIT-0 texts and names MIT-0 in its
  licence.

After publication, published-templates.yml and bun-deno-published.yml check
the release from the public registry.

Licence

MIT, plus MIT-0 for the starter code. See LICENSING.md.