From ce496e04facd4759b10d06c00b8ee9ee5f371656 Mon Sep 17 00:00:00 2001 From: semantic-release-bot Date: Fri, 4 Nov 2022 21:45:23 +0000 Subject: [PATCH] chore(release): 2.0.0-v3-studio.8 [skip ci] --- CHANGELOG.md | 6 ++++++ package-lock.json | 4 ++-- package.json | 2 +- 3 files changed, 9 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 3a81488..b75e04a 100644 --- 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.8](https://github.com/sanity-io/sanity-studio-secrets/compare/v2.0.0-v3-studio.7...v2.0.0-v3-studio.8) (2022-11-04) + +### Bug Fixes + +- **deps:** pkg-utils & @sanity/plugin-kit ([5bd94d5](https://github.com/sanity-io/sanity-studio-secrets/commit/5bd94d55b9369044e7a841d6300021af2f3fa7ca)) + ## [2.0.0-v3-studio.7](https://github.com/sanity-io/sanity-studio-secrets/compare/v2.0.0-v3-studio.6...v2.0.0-v3-studio.7) (2022-11-03) ### Bug Fixes diff --git a/package-lock.json b/package-lock.json index e22d715..406a7e4 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "@sanity/studio-secrets", - "version": "2.0.0-v3-studio.7", + "version": "2.0.0-v3-studio.8", "lockfileVersion": 2, "requires": true, "packages": { "": { "name": "@sanity/studio-secrets", - "version": "2.0.0-v3-studio.7", + "version": "2.0.0-v3-studio.8", "license": "MIT", "dependencies": { "@sanity/incompatible-plugin": "^1.0.4" diff --git a/package.json b/package.json index ce8eadd..4c1442e 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@sanity/studio-secrets", - "version": "2.0.0-v3-studio.7", + "version": "2.0.0-v3-studio.8", "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.", "homepage": "https://github.com/sanity-io/sanity-studio-secrets#readme", "bugs": {