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

CHANGELOG.md

@@ -5,6 +5,20 @@
 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.1](https://github.com/sanity-io/sanity-studio-secrets/compare/v1.1.0-v3-studio.1...v2.0.0-v3-studio.1) (2022-10-28)
+
+### ⚠ BREAKING CHANGES
+
+- package is now named @sanity/secrets instead of sanity-secrets
+
+### Features
+
+- renamed package to @sanity/secrets ([6fb61e4](https://github.com/sanity-io/sanity-studio-secrets/commit/6fb61e45610d72976e1aefe5ed08d7141f7884ea))
+
+### Bug Fixes
+
+- **release:** v3 release ([4d94493](https://github.com/sanity-io/sanity-studio-secrets/commit/4d944930b33b9b4aa16a124c948a2224550395f2))
+
 ## [1.1.0-v3-studio.1](https://github.com/sanity-io/sanity-studio-secrets/compare/v1.0.0...v1.1.0-v3-studio.1) (2022-10-28)
 
 ### Features

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sanity/secrets",
-  "version": "1.1.0-v3-studio.1",
+  "version": "2.0.0-v3-studio.1",
   "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",