chore: release packages

[btravers]

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

@btravstack/[email protected]

Minor Changes

• 1af25ee: Breaking: an aggregate's decision now carries everything a repository
  needs to save it.

  • Entity.Decision gains expectedVersion, the version the store must still
    be at, and its events now hold every event decided since the aggregate
    was loaded. A chain of commands saves as one decision without losing the
    earlier events; reusing an already-saved state yields a conflict, never an
    overwrite.
  • An aggregate's make requires the version: make(row, { version }).
    replay takes the stream's length, and start is version 0.
  • The version is kept beside the instance, not on it: no reserved field name,
    nothing in toJSON(), and the package never interprets the number.

  To migrate, pass { version } to an aggregate's make, and drop the separate
  version argument from a repository's save: read decision.expectedVersion
  instead. Entity's make is unchanged.

• 2370c4d: Breaking: Entity.aggregate now requires at least one field flagged
  identity: true. An aggregate root is what other aggregates reference and what
  a repository loads, so a field map without one is a compile error, and a
  declaration that gets past the types throws while it runs. sameIdentityAs is
  therefore always available on an aggregate.

  To migrate, flag the aggregate's id: id: Entity.field(SomeId, { identity: true }).
  Entity is unchanged: identity stays optional there.

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 5 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

• Configuration used: Repository: btravstack/entity/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: 2e7aee20-e43a-4b34-a9ae-b6f069c1354a

📥 Commits

Reviewing files that changed from the base of the PR and between 9b65d46 and 0a6e28d.

📒 Files selected for processing (4)

• .changeset/aggregate-carries-version.md
• .changeset/aggregate-requires-identity.md
• packages/entity/CHANGELOG.md
• packages/entity/package.json

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Copilot review overview

🟢 Approval recommended

It is a mechanically-generated release that only bumps the version and moves verified-matching changeset content into the changelog, with all consistency checks passing.

Review effort: Balanced
Findings: None

What changed in this PR

This is an automated release PR generated by the Changesets GitHub Action to publish @btravstack/[email protected]. It consumes the two pending minor changesets, bumps the package version, and folds their content into the changelog. It fits into the repo's release workflow: merging it triggers the npm publish of the new version.

Changes:

• Bumps packages/entity version from 0.8.0 to 0.9.0 (correct, since the highest pending bump is minor).
• Prepends a ## 0.9.0 entry to CHANGELOG.md documenting the two breaking aggregate changes (version-carrying decisions; aggregates requiring an identity field).
• Deletes the two now-consumed changeset files.

File	Description
packages/​entity/​package.json	Version bump 0.8.0 → 0.9.0, consistent with the consumed minor changesets
packages/​entity/​CHANGELOG.md	New 0.9.0 section; content matches the two deleted changesets verbatim
.changeset/​aggregate-requires-identity.md	Removed after being folded into the changelog
.changeset/​aggregate-carries-version.md	Removed after being folded into the changelog

I verified: the version bump matches the two minor changesets, the changelog text is identical to the consumed changeset files (including commit hashes 1af25ee and 2370c4d), the heading format is consistent with the prior ## 0.8.0 entry, no stray 0.8.0 references remain anywhere, and all workspace dependents pin via workspace:* so no downstream version updates are needed.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.