Skip to content

Set up Changesets for versioning#3

Merged
gentamura merged 1 commit intomainfrom
chore/setup-changesets
Oct 3, 2025
Merged

Set up Changesets for versioning#3
gentamura merged 1 commit intomainfrom
chore/setup-changesets

Conversation

@gentamura
Copy link
Member

@gentamura gentamura commented Oct 3, 2025

Summary

  • add @changesets/cli and initialize the .changeset/ configuration
  • expose package.json scripts for changeset workflows (changeset, version-packages, release)
  • configure packages for public access via Changesets

Testing

  • bun run lint
  • bun test

@coderabbitai
Copy link

coderabbitai bot commented Oct 3, 2025

Walkthrough

Adds Changesets tooling: introduces .changeset directory with README and config, and updates package.json to include Changesets CLI as a devDependency plus scripts for creating changesets, versioning, and releasing.

Changes

Cohort / File(s) Summary of Changes
Changesets setup
/.changeset/README.md, /.changeset/config.json
Added README explaining Changesets and a config JSON defining schema, changelog path, baseBranch main, public access, and workflow options (no commit, empty fixed/linked/ignore, updateInternalDependencies patch).
NPM scripts & dev tooling
/package.json
Added devDependency @changesets/cli and scripts: changeset, version-packages, release; minor formatting update to scripts block.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I thump the ground—release in sight,
New scripts nibble through the night.
A patch, a hop, versioned delight,
Changesets lanterns glowing bright.
Crunching carrots, shipping right! 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title succinctly describes the primary change of introducing Changesets for versioning, is concise, and clearly conveys the main intent without extraneous detail.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/setup-changesets

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@gentamura gentamura self-assigned this Oct 3, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)
package.json (2)

7-11: Pin catalog versions (remove carets) to comply with repo policy

Catalog entries should be pinned exactly, not with ranges. As per coding guidelines

Apply this diff:

-    "drizzle-orm": "^0.44.5",
-    "hono": "^4.4.4",
-    "postgres": "^3.4.7",
-    "jose": "^5.2.3"
+    "drizzle-orm": "0.44.5",
+    "hono": "4.4.4",
+    "postgres": "3.4.7",
+    "jose": "5.2.3"

7-14: Fix incomplete catalog references in workspace packages

  • packages/api/package.json (line 20): replace "hono": "catalog:" with "hono": "catalog:hono".
  • packages/auth/package.json (line 18): replace "jose": "catalog:" with "jose": "catalog:jose".
  • packages/db/package.json (lines 17–18): replace
    • "drizzle-orm": "catalog:""drizzle-orm": "catalog:drizzle-orm"
    • "postgres": "catalog:""postgres": "catalog:postgres"
🧹 Nitpick comments (2)
.changeset/README.md (1)

1-8: Add repo-specific guidance on SemVer and breaking changes

Include a short note that contributors must add a Changeset for user-visible changes and declare breaking changes per SemVer. This aligns team expectations. As per coding guidelines

.changeset/config.json (1)

2-10: Confirm commit: false is intentional

With commit: false, changeset version won’t create a commit; you’ll need to commit bumped files manually/CI. If you want automatic commits during versioning, set it to true. Also consider defining linked groups if packages should version in lockstep.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 72afbf0 and 0701d05.

⛔ Files ignored due to path filters (1)
  • bun.lock is excluded by !**/*.lock
📒 Files selected for processing (3)
  • .changeset/README.md (1 hunks)
  • .changeset/config.json (1 hunks)
  • package.json (1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
package.json

📄 CodeRabbit inference engine (AGENTS.md)

package.json: Pin shared dependency versions in the root package.json catalog
Add new shared dependencies to the root catalog before consuming them in packages

Files:

  • package.json
.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/README.md
  • .changeset/config.json
🔇 Additional comments (1)
package.json (1)

18-21: Scripts LGTM

Scripts for creating/versioning/publishing Changesets look correct for a Bun workspace.

@gentamura gentamura merged commit 526cf57 into main Oct 3, 2025
4 checks passed
@gentamura gentamura deleted the chore/setup-changesets branch October 3, 2025 13:27
This was referenced Oct 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant