chore: remove release docs (#41)

digidem · Jan 13, 2025 · f0147c6 · f0147c6
1 parent 02c0231
commit f0147c6
Show file tree

Hide file tree

Showing 4 changed files with 154 additions and 2,154 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md
@@ -13,23 +13,3 @@ npm install
 ## Running tests
 
 Unit tests can be run using `npm test` (or `npm t`).
-
-## Releases
-
-Currently releases are done locally via the CLI. We use [commit-and-tag-version](https://github.com/absolute-version/commit-and-tag-version) to handle version bumping and changelog generation.
-
-Some helpful commands:
-
-- `npx commit-and-tag-version --dry-run`: perform a dry-run release. If you're trying to figure out the desired options for performing a release, it's generally a good idea to specify this `--dry-run` flag for any command you do.
-
-- `npx commit-and-tag-version`: create a release. This will bump the version and update the changelog file. At the end of the command's output it will tell you the command to run to actually push the changes and publish the release to npm. Usually it's something like:
-
-  ```sh
-  Run `git push --follow-tags origin main` to publish
-  ```
-
-  In order to publish to npm, you'll have to run the following:
-
-  ```sh
-  npm publish --access=public
-  ```