Use changesets

Author: saoudrizwan

.changes/header.tpl.md

@@ -0,0 +1,8 @@
+# Changesets
+
+Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
+with multi-package repos, or single-package repos to help you version and publish your code. You can
+find the full documentation for it [in our repository](https://github.com/changesets/changesets)
+
+We have a quick list of common questions to get you started engaging with this project in
+[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)

.changes/unreleased/.gitkeep

@@ -0,0 +1,11 @@
+{
+	"$schema": "https://unpkg.com/@changesets/[email protected]/schema.json",
+	"changelog": "@changesets/cli/changelog",
+	"commit": false,
+	"fixed": [],
+	"linked": [],
+	"access": "restricted",
+	"baseBranch": "main",
+	"updateInternalDependencies": "patch",
+	"ignore": []
+}

.changes/unreleased/Added-20250129-010730.yaml

@@ -163,24 +163,24 @@ To contribute to the project, start with our [Contributing Guide](CONTRIBUTING.m
 <details>
 <summary>Creating a Pull Request</summary>
 
-1. Before creating a PR, generate a changelog entry using [Changie](https://changie.dev/):
+1. Before creating a PR, generate a changeset entry:
     ```bash
-    npm run changie new
+    npm run changeset
     ```
    This will prompt you for:
-   - Kind of change (Added, Changed, Deprecated, Removed, Fixed, Security)
-     - `Added` → triggers minor version bump (1.0.0 → 1.1.0)
-     - `Changed`, `Deprecated`, `Removed`, `Fixed`, `Security` → triggers patch version bump (1.0.0 → 1.0.1)
-     - Breaking changes → triggers major version bump (1.0.0 → 2.0.0)
+   - Type of change (major, minor, patch)
+     - `major` → breaking changes (1.0.0 → 2.0.0)
+     - `minor` → new features (1.0.0 → 1.1.0)
+     - `patch` → bug fixes (1.0.0 → 1.0.1)
    - Description of your changes
-   - Issue number (if applicable)
 
-2. Commit your changes and the generated `.changes` file
+2. Commit your changes and the generated `.changeset` file
 
 3. Push your branch and create a PR on GitHub. Our CI will:
    - Run tests and checks
-   - When merged to main, automatically batch changelog entries
-   - Create a version PR with the updated CHANGELOG.md
+   - Changesetbot will create a comment showing the version impact
+   - When merged to main, changesetbot will create a Version Packages PR
+   - When the Version Packages PR is merged, a new release will be published
 
 </details>