[ci] release

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@marko/[email protected]

Major Changes

• #1980 9d3b34eef Thanks @DylanPiercey! - Allow parse errors to be recovered from by migrations. This adds a new ast node type of MarkoParseError.
  MarkoParseError nodes can be removed during the migration stage to handle legacy syntaxes. Any MarkoParseError
  left in the AST at the end of the migration phase will throw an error similar to what it would have previously
  thrown synchronously.

  This also means that all parse errors can be surfaced as an aggregate error instead of bailing on the first
  parse error. When the compiler is ran with errorRecovery: true these errors become diagnostics instead of
  being thrown.

@marko/[email protected]

Minor Changes

• #1980 9d3b34eef Thanks @DylanPiercey! - Allow parse errors to be recovered from by migrations. This adds a new ast node type of MarkoParseError.
  MarkoParseError nodes can be removed during the migration stage to handle legacy syntaxes. Any MarkoParseError
  left in the AST at the end of the migration phase will throw an error similar to what it would have previously
  thrown synchronously.

  This also means that all parse errors can be surfaced as an aggregate error instead of bailing on the first
  parse error. When the compiler is ran with errorRecovery: true these errors become diagnostics instead of
  being thrown.

Patch Changes

• Updated dependencies [9d3b34eef]:
  • @marko/[email protected]

[email protected]

Minor Changes

• #1980 9d3b34eef Thanks @DylanPiercey! - Allow parse errors to be recovered from by migrations. This adds a new ast node type of MarkoParseError.
  MarkoParseError nodes can be removed during the migration stage to handle legacy syntaxes. Any MarkoParseError
  left in the AST at the end of the migration phase will throw an error similar to what it would have previously
  thrown synchronously.

  This also means that all parse errors can be surfaced as an aggregate error instead of bailing on the first
  parse error. When the compiler is ran with errorRecovery: true these errors become diagnostics instead of
  being thrown.

Patch Changes

• #1980 20deb5699 Thanks @DylanPiercey! - Fix issue that could happen if DOMContentLoaded was manually invoked multiple times.

• Updated dependencies [9d3b34eef]:

  • @marko/[email protected]
  • @marko/[email protected]

@marko/[email protected]

Minor Changes

• #1980 9d3b34eef Thanks @DylanPiercey! - Allow parse errors to be recovered from by migrations. This adds a new ast node type of MarkoParseError.
  MarkoParseError nodes can be removed during the migration stage to handle legacy syntaxes. Any MarkoParseError
  left in the AST at the end of the migration phase will throw an error similar to what it would have previously
  thrown synchronously.

  This also means that all parse errors can be surfaced as an aggregate error instead of bailing on the first
  parse error. When the compiler is ran with errorRecovery: true these errors become diagnostics instead of
  being thrown.

Patch Changes

• Updated dependencies [9d3b34eef]:
  • @marko/[email protected]