Merge branch 'main' into feature/post-selector-filters

Author: mogmarsh

README.md

@@ -59,15 +59,25 @@ To add a package manually you can create a new directory with the same name as t
 
 ## Versioning and Publishing Packages in this Monorepo
 
-This project uses the [Changesets CLI](https://github.com/changesets/changesets) to manage versioning and publishing of packages in this monorepo. To release a new version of a package that you are working on, you can run the following command:
+This project uses the [Changesets CLI](https://github.com/changesets/changesets) to manage versioning and publishing of packages in this monorepo.
+
+It is recommended to create a changeset for each feature or bug fix that is added to a package. This will help keep track of changes and ensure that the version of the package is updated correctly.
+
+To create a changeset, run the following command in the root of the monorepo:
 
 ```sh
-npx changeset
+npm run changeset
 ```
-
 The command above will walk through some prompts and create a new changeset file in the `.changeset` directory. Commit this file to version control in your feature branch and open a pull request.
 
-Once the pull request is approved, merge the branch into the `main` branch. The changeset Github actions will automatically create a new branch, e.g. `changeset-release/main` and pull request titled "Version Packages". Once you are ready to release the package merge the pull request. You may need to check with other developers releasing versions for other packages as the changeset release will add all changes to that pull request. Once the `changeset-release/main` branch is merged it will publish the new version of the package to the NPM registry.
+## Example Workflow
+1. Create a new branch from `main` for the feature you are working on.
+2. Make changes to the package and commit them to the branch.
+3. Create a pull request and request a review.
+4. Once approved, create a changeset by running `npm run changeset` and commit the changeset file to your feature branch.
+5. Merge the feature branch into `main`.
+
+Once merged into the `main` branch, the changeset Github action will automatically create a new branch, e.g. `changeset-release/main` and pull request titled "Version Packages". A new version of this package is not published until this pull request is merged.
 
 **You do not need to manually bump the version of the package in the `package.json` file. The changeset Github actions will handle this for you.**