From 6fb61e45610d72976e1aefe5ed08d7141f7884ea Mon Sep 17 00:00:00 2001 From: Snorre Eskeland Brekke Date: Fri, 28 Oct 2022 13:58:11 +0200 Subject: [PATCH] feat!: renamed package to @sanity/secrets BREAKING CHANGE: package is now named @sanity/secrets instead of sanity-secrets --- package-lock.json | 4 ++-- package.json | 7 +------ 2 files changed, 3 insertions(+), 8 deletions(-) diff --git a/package-lock.json b/package-lock.json index 732591d..df05396 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,11 +1,11 @@ { - "name": "sanity-secrets", + "name": "@sanity/secrets", "version": "1.1.0-v3-studio.1", "lockfileVersion": 2, "requires": true, "packages": { "": { - "name": "sanity-secrets", + "name": "@sanity/secrets", "version": "1.1.0-v3-studio.1", "license": "MIT", "dependencies": { diff --git a/package.json b/package.json index 46dd23c..c974db2 100644 --- a/package.json +++ b/package.json @@ -1,5 +1,5 @@ { - "name": "sanity-secrets", + "name": "@sanity/secrets", "version": "1.1.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 ", @@ -77,10 +77,5 @@ }, "dependencies": { "@sanity/incompatible-plugin": "^1.0.4" - }, - "sanityPlugin": { - "verifyPackage": { - "packageName": false - } } }