Release 0.2.2

[gentamura]

Summary

• add changeset to release @listee/* packages as 0.2.2 with dist-based publish config

Summary by CodeRabbit

• Chores
  • Declared patch updates for multiple core packages to facilitate improved distribution manifest publishing.

[coderabbitai]

Walkthrough

A changeset file is added declaring patch version updates for four packages (@listee/api, @listee/auth, @listee/db, @listee/types), specifying that each package should publish from its dist manifest to ensure npm tarballs include resolved semver dependencies.

Changes

Cohort / File(s)	Summary
Changeset Configuration .changeset/publish-dist-manifests.md	Patch version changeset for @listee/api, @listee/auth, @listee/db, @listee/types. Notes that packages should publish from dist manifests to ensure npm tarballs contain semver dependencies.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Add turbo build orchestration and dist manifest tooling #6: Adds postbuild write-dist-manifest tooling and aligns package publishing to dist manifests, establishing the infrastructure this changeset documents.
• Release v0.2.1 #25: Modifies release metadata for the same four packages to ensure dist manifests include resolved workspace/catalog dependencies as semver ranges.
• Use dist manifests for publish #27: Targets the identical change—enabling the four packages to publish from their dist manifests via publishConfig.directory configuration.

Poem

🐰 Four packages hop in line,
Patch updates mark the time,
From dist they'll dance with care,
Semver deps float through the air! ✨
Version tales written fair.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

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.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "Release 0.2.2" directly aligns with the primary objective of the pull request, which is to add a changeset declaring four packages as patch updates for version 0.2.2. The title is concise, specific, and clearly communicates the main purpose of the change without unnecessary noise or vague terminology. While the title doesn't mention every aspect of the changeset (such as the dist manifest publish configuration), this level of detail is not required for an effective title, as the core change—releasing version 0.2.2—is accurately captured.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release/0.2.2

---

📜 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 b679cef and 35a2a3f.

📒 Files selected for processing (1)

• .changeset/publish-dist-manifests.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/publish-dist-manifests.md

🧠 Learnings (1)

📚 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/publish-dist-manifests.md

🔇 Additional comments (1)

.changeset/publish-dist-manifests.md (1)

1-8: Well-structured changeset with clear rationale.

The changeset correctly declares patch-level updates for all four @Listee packages and provides clear documentation of the intent. The message aligns with best practices by explaining why the dist manifest publishing is needed—to ensure npm tarballs include resolved semver dependencies. This is consistent with the learning about using dist manifests for proper semver dependency handling.

---

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.}