chore(release): 2.0.0-v3-studio.5 [skip ci]

CHANGELOG.md

@@ -5,6 +5,12 @@
 All notable changes to this project will be documented in this file. See
 [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+## [2.0.0-v3-studio.5](https://github.com/sanity-io/sanity-studio-secrets/compare/v2.0.0-v3-studio.4...v2.0.0-v3-studio.5) (2022-10-31)
+
+### Bug Fixes
+
+- renamed package to @sanity/studio-secrets ([0a5aa16](https://github.com/sanity-io/sanity-studio-secrets/commit/0a5aa16d19ec2f3962a9b757af3c011fdcd3b3e5))
+
 ## [2.0.0-v3-studio.4](https://github.com/sanity-io/sanity-studio-secrets/compare/v2.0.0-v3-studio.3...v2.0.0-v3-studio.4) (2022-10-30)
 
 ### Bug Fixes

package.json

@@ -3,7 +3,7 @@
   "publishConfig": {
     "access": "public"
   },
-  "version": "2.0.0-v3-studio.4",
+  "version": "2.0.0-v3-studio.5",
   "description": "React hooks and UI for reading and managing secrets in a Sanity Studio. This is a good pattern for keeping configuration secret. Instead of using environment variables which would be bundled with the Studio source (it is an SPA), we store secret information in a document in the dataset. This document will not be readable to externals even in a public dataset. With custom access controls you can also specify which users can read the configuration in your Studio.",
   "author": "Sanity.io <hello@sanity.io>",
   "license": "MIT",