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

sanity-io · Oct 30, 2022 · f1a7211 · f1a7211
1 parent 96f95f1
commit f1a7211
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 3 deletions.
diff --git a/CHANGELOG.md b/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.3](https://github.com/sanity-io/sanity-studio-secrets/compare/v2.0.0-v3-studio.2...v2.0.0-v3-studio.3) (2022-10-30)
+
+### Bug Fixes
+
+- corrected storeSecret key ([96f95f1](https://github.com/sanity-io/sanity-studio-secrets/commit/96f95f1c6f23f2f977f53b1827262cdd9a2ef1e1))
+
 ## [2.0.0-v3-studio.2](https://github.com/sanity-io/sanity-studio-secrets/compare/v2.0.0-v3-studio.1...v2.0.0-v3-studio.2) (2022-10-28)
 
 ### Bug Fixes

diff --git a/package-lock.json b/package-lock.json
diff --git a/package.json b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@sanity/secrets",
-  "version": "2.0.0-v3-studio.2",
+  "version": "2.0.0-v3-studio.3",
   "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",