Release v0.2.1

[gentamura]

Summary

• publish package metadata fixes (README/LICENSE ship with npm tarballs)
• resolve workspace/catalog references to semver ranges in dist manifests
• add validation to prevent unresolved references during publish

Testing

• bun run lint
• bun test
• bun run build

Summary by CodeRabbit

• Chores
  • Released patch versions for API, Auth, Database, and Types packages to include package metadata in npm publishes and improve dependency resolution in generated distribution manifests.

[coderabbitai]

Walkthrough

A patch release entry was added to the changeset for four packages (@listee/api, @listee/auth, @listee/db, @listee/types), documenting changes to include package metadata files in npm publishes and resolve catalog/workspace dependencies to semver ranges in generated dist manifests.

Changes

Cohort / File(s)	Summary
Changeset patch release entry .changeset/patch-release.md	Adds patch release metadata for four packages with changelog describing inclusion of package metadata files in npm publishes and resolution of catalog/workspace dependencies to semver ranges in dist manifests

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Include docs and semver dependencies in published packages #24: Directly implements the changes documented in this patch release entry (package metadata inclusion in npm publishes and workspace dependency resolution in dist manifests).
• Add repository metadata for packages #22: Modifies package manifest metadata by adding repository fields to package.json, affecting package publish configuration.
• Add package READMEs and MIT licenses #23: Updates package metadata intended for npm publishes including license fields and README files.

Poem

🐰 A changelog hops into place,
Four packages mark their pace,
Metadata files now publish bright,
Workspace deps resolve just right! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Title Check	❓ Inconclusive	The title "Release v0.2.1" is technically related to the changeset as it does refer to a release PR, but it is extremely vague and generic. While the PR description details specific changes (package metadata fixes, workspace/catalog dependency resolution, and validation additions), the title conveys only a version number without describing any of the actual substantive changes. A teammate scanning the commit history would not understand what was fixed or improved in this release without reading the full PR description. This matches the criterion of a vague or generic title that uses non-descriptive terms without conveying meaningful information about the changeset.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release/v0.2.1

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between be4eb71 and fa3586b.

📒 Files selected for processing (1)

• .changeset/patch-release.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

.changeset/**

📄 CodeRabbit inference engine (AGENTS.md)

.changeset/**: Attach the latest Changeset entry when a release is required
Declare breaking changes and follow SemVer in Changesets

Files:

• .changeset/patch-release.md

🧠 Learnings (2)

📚 Learning: 2025-10-02T12:40:33.718Z

Learnt from: CR
PR: listee-dev/listee-libs#0
File: AGENTS.md:0-0
Timestamp: 2025-10-02T12:40:33.718Z
Learning: When publishing npm packages, build/pack with Bun (bun pm pack / bun publish) so catalog references collapse to semver ranges

Applied to files:

• .changeset/patch-release.md

📚 Learning: 2025-10-02T12:40:33.718Z

Learnt from: CR
PR: listee-dev/listee-libs#0
File: AGENTS.md:0-0
Timestamp: 2025-10-02T12:40:33.718Z
Learning: Applies to packages/*/package.json : Reference shared dependencies via the "catalog:" protocol in package manifests

Applied to files:

• .changeset/patch-release.md

🔇 Additional comments (1)

.changeset/patch-release.md (1)

1-8: Changeset is properly formatted and SemVer-aligned.

The patch release declaration for all four packages is appropriate. Metadata file inclusion and catalog/workspace dependency resolution are both non-breaking, maintenance-level fixes that warrant patch version bumps. The changelog description accurately reflects the PR objectives.

---

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 and usage tips.}