chore(release): 3.0.2 [skip ci]

Author: semantic-release-bot

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.
 
+## [3.0.2](https://github.com/sanity-io/sanity-studio-secrets/compare/v3.0.1...v3.0.2) (2025-07-10)
+
+### Bug Fixes
+
+- **deps:** allow studio v4 in peer dep ranges ([#22](https://github.com/sanity-io/sanity-studio-secrets/issues/22)) ([185ec8b](https://github.com/sanity-io/sanity-studio-secrets/commit/185ec8bb5604abb49b91661b620fe073ffe55b36))
+
 ## [3.0.1](https://github.com/sanity-io/sanity-studio-secrets/compare/v3.0.0...v3.0.1) (2024-12-17)
 
 ### Bug Fixes

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2024 Sanity.io
+Copyright (c) 2025 Sanity.io
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package-lock.json

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