Use pnpm instead of NPM for releases

.changeset/famous-humans-notice.md

@@ -0,0 +1,5 @@
+---
+'@secure-ci/core': patch
+---
+
+Publish with pnpm instead of npm

.github/workflows/release.yml

@@ -36,7 +36,7 @@ jobs:
         id: changesets
         uses: changesets/action@v1
         with:
-          publish: npm publish --provenance --access public
+          publish: pnpm publish --provenance --access public
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

CONTRIBUTING.md

@@ -16,4 +16,6 @@ You can run `pnpm lint` for the linter and check the [solidity style guides](htt
 Also, even though we do CI testing,
 please test your code and ensure that it builds locally before submitting a pull request.
 
+After you create your change you can run `pnpm changeset` to create the changelog
+
 Thank you for your help!

README.md

@@ -84,16 +84,7 @@ pnpm save:deployments
 
 We use [changesets](https://www.npmjs.com/package/@changesets/cli) to manage the versioning and publishing of the packages
 
-First you need to create the changeset and then apply it
-
-```bash
-// Create a new changeset
-pnpm changeset
-// Apply the changeset
-pnpm changeset version
-```
-
-After the PR with the changes is merge we create a release in GitHub and the workflow will publish the package
+Publishing and versioning is done automatically by the CI/CD pipeline
 
 ### Development: