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/di@0.1.1

Patch Changes

• 6384640: Fix TS4020 in consumers that export a port. export class OrderRepository extends Port("OrderRepository")<Shape> {} — the pattern the README teaches — could not emit
  declarations: the emitter had no name for the heritage expression's type, so it expanded
  down to PortInstance's module-private unique symbol brands and reported "has or is
  using private name 'ID'". PortClass and ManyPortClass are now exported as types, which
  gives the emitter a name to stop at. The brand symbols themselves stay unexported, so port
  identity remains nominal and a port instance remains unforgeable.

[Copilot]

Pull request overview

Release PR generated by Changesets to publish @btravstack/di@0.1.1, capturing the patch note about fixing TS4020 declaration emit issues for consumers exporting ports.

Changes:

• Bump @btravstack/di version from 0.1.0 to 0.1.1.
• Add packages/di/CHANGELOG.md entry describing the TS4020 fix.
• Remove the consumed changeset file after generating the release notes.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
packages/di/package.json	Version bump to 0.1.1 for the release.
packages/di/CHANGELOG.md	New changelog entry for 0.1.1 patch release.
.changeset/fresh-pears-smoke.md	Removed consumed changeset as part of the release workflow.

---

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

[btravers]

Stale: the changeset this PR versioned (6384640) was replaced by the empty no-release-first-publish.md in #5, and 0.1.0 was published directly with the fix included. Every changeset on main is now empty, so the release action skips PR creation ("All changesets are empty; not creating PR") and never refreshes this leftover. Closing; the action will open a fresh release PR when the next real changeset lands on main.