[leonidaz]

Summary

The next @tsrx/core release will be a minor, 0.5.0, not a patch. This PR changes the bump in #713's changeset (parser-spread-argument-markup.md) from patch to minor. Every other pending changeset stays patch. @tsrx/core is alone in its fixed group, so only core gets the minor. Packages that depend on it get patch bumps with updated ranges (updateInternalDependencies: patch), as usual. The Version Packages PR (#546) picks this up once it merges.

Why

The repository's rule is minor for language or public API removals, and this release changes the language:

• fix(core): read an element in a spread attribute's argument or an attribute value without braces as template markup (#656) #713: an element in a spread attribute's argument (<div {...{ k: <b>…</b> }} />) or in an unbraced attribute value (<div k=<b>…</b> />) is template markup, no longer plain JSX. A comment in it is a comment, and directives in it are directives. Compilers that visit these elements as plain JSX break. Ripple's server build throws Not implemented: JSXElement for a spread argument's element (Upgrading to the next @tsrx/core: template text parsing (tsrx-org/tsrx#711), spread-argument markup on the server, and a decoded JSXText.value (tsrx-org/tsrx#710) Ripple-TS/ripple#1520).
• Code that used to parse is now rejected:
  • fix(core): read tokens by their context like TSX: comments after directive keywords, yield @…, />/, </ after an operand, and subscripts after elements (#477, #547, #584, #586, #426) #635: <b />.foo, a </re/;
  • fix(core): read type arguments after superclasses and class and function expressions, and reject what follows export or decorates an array pattern (#523, #545, #578, #607, #609, #631) #650: decorators in array destructuring;
  • fix(core): collect parameter property, empty for head, and let name mistakes that TypeScript reports from its checker, and reject decorators on object literal members (#644, #645, #646) #666: decorators on object members;
  • an @if, @for or @try body still open at the end of the input.
• fix(core): read abstract before any declaration, export default interface across a line break, type as, export global and escaped keywords as TypeScript does (#697, #698, #699, #700, #709) #721 and fix(core): read an async arrow function's optional rest parameter, report a generic arrow function's errors where they are, collect a signature parameter's default, and reject async(a)(b) => and type assertions in arrow parameters (#702, #703, #704, #705, #706) #728, if they merge before the release, reject more code that TypeScript rejects, such as async(a)(b) => 1 and (x as T) => x.

With a patch, the targets' ^0.4.0 ranges would pick all of this up in a lockfile refresh. With a minor, consumers upgrade on purpose:

• Ripple pins ^0.3.3. Its upgrade issue is Upgrading to the next @tsrx/core: template text parsing (tsrx-org/tsrx#711), spread-argument markup on the server, and a decoded JSXText.value (tsrx-org/tsrx#710) Ripple-TS/ripple#1520.
• Octane pins ^0.4.0. Its upgrade issue is being filed.

Decided by the maintainer on 2026-09-26.

Validation

• node scripts/check-changesets.js passes.
• Only the changeset changed; no code changed.

🤖 Generated with Claude Code

---

Note

Low Risk
Only the changeset bump type changes; release tooling and consumer upgrade semantics are affected, not product code in this PR.

Overview
Release metadata only: the pending changeset for parser spread/unbraced-attribute markup (parser-spread-argument-markup.md) now declares @tsrx/core: minor instead of patch, so the next core release is 0.5.0 rather than a patch on 0.4.x.

That aligns versioning with breaking-ish language/parser behavior already described in the changeset (and related rejections noted in the PR): consumers on ^0.4.0 should opt into the minor instead of picking it up via a routine patch/lockfile refresh. No runtime or parser code changes in this diff.

^{Reviewed by Cursor Bugbot for commit 7cb8e69. Bugbot is set up for automated code reviews on this repo. Configure here.}