Version 12.0.0

The primary breaking change is to the format of the imported/exported biblio, in #425. Using this version with the ecma262 biblio will require major version 2 of @tc39/ecma262-biblio.

A secondary breaking change in #426 is that the "user code" annotation is only rendered when using the --mark-effects cli flag or putting markEffects: true in the programmatic options or metadata.

Other changes:

• effects are now propagated in the biblio: #426
• support for redefinition in structured headers: #428

Version 11.0.1

• fix searching for clause numbers in #423
• bump chalk in #422

Version 11.0.0

There's a breaking change to the linter, changing the convention for comparisons against floating-point zero: #424.

Version 10.0.2

• Revert "ecmascript spelling" by @bakkot in #413

Version 10.0.1

(fixes a typo in package.json, sigh)

Version 10.0.0

This is a major release containing several breaking changes.

Most notably, ecmarkup no longer ships with a (stale) built-in copy of the biblio for ecma262. Proposals which upgrade will therefore not automatically link against that specification. The plan is to start distributing the biblio for ecma262 as a seperate artifact (on npm), updated whenever the spec is updated. (Follow along at #251.) Until that's available proposals probably should not upgrade.

Other changes:

• there is now a bare-bones typechecker (guarded behind --lint-spec) which enforces certain invariants around the use of completion records in AOs, as discussed in tc39/ecma262#2547
• the CLI has been tweaked:
  • it will now error if passed an argument it does not recognize, instead of silently ignoring it
  • the --biblio flag has been replaced with the more explicit --write-biblio
  • a new --load-biblio flag has been added which allows you to specify a path or npm package from which to load a biblio
  • --lint-formatter has been renamed to the more accurate --error-formatter and --would-write to the more descriptive --expand-glob.
• eslint is no longer included as a dependency, so if you were using the --lint-formatter CLI flag with a built-in formatter you may need to add eslint as a dependency (the default codeframe formatter is still included)
• the format of the exported biblio has changed slightly

Nontrivial PRs:

• ecmascript spelling #407
• switch from nomnom to command-line-args #376
• remove runtime dependency on eslint by depending on the codeframe formatter directly #377
• Bump various dependencies #378
• some tweaks to the biblio #405
• rename some cli flags #406
• completion-record local typechecking #408

Version 9.8.1

Fix header parser in #403

Version 9.8.0

Add shortcuts help dialog in #400

Version 9.7.1

• Fix propagation of "result of evaluating code" effects, in #393
• Ensure emu-meta tags are fenced by the same mechanisms that xrefs are, in #395

Version 9.7.0

The only consumer-facing change is the addition of the [fence-effects=""] step attribute to stop effect propagation in #388