Skip to content

Commit

Permalink
chore(release): 2.0.2 [skip ci]
Browse files Browse the repository at this point in the history
  • Loading branch information
semantic-release-bot committed Nov 25, 2022
1 parent f332be9 commit adc34dc
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 3 deletions.
6 changes: 6 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.2](https://github.com/sanity-io/sanity-studio-secrets/compare/v2.0.1...v2.0.2) (2022-11-25)

### Bug Fixes

- **deps:** sanity ^3.0.0 (rc.3 compatible) ([f332be9](https://github.com/sanity-io/sanity-studio-secrets/commit/f332be965b008a9a8872666f6f89585d73fcad44))

## [2.0.1](https://github.com/sanity-io/sanity-studio-secrets/compare/v2.0.0...v2.0.1) (2022-11-15)

### Bug Fixes
Expand Down
4 changes: 2 additions & 2 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@sanity/studio-secrets",
"version": "2.0.1",
"version": "2.0.2",
"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": {
Expand Down

0 comments on commit adc34dc

Please sign in to comment.