Socket
Socket
Sign inDemoInstall

@sanity/incompatible-plugin

Package Overview
Dependencies
126
Maintainers
33
Versions
7
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

Comparing version 1.0.0 to 1.0.1

10

package.json
{
"name": "@sanity/incompatible-plugin",
"version": "1.0.0",
"version": "1.0.1",
"description": "Display an error dialog in Sanity Studio v2 when a v3 plugin has been installed.",

@@ -30,5 +30,5 @@ "source": "./src/index.tsx",

"dependencies": {
"@sanity/icons": "^1.3.0",
"@sanity/ui": "^0.37.0",
"react-copy-to-clipboard": "^5.0.0"
"@sanity/icons": "^1.3.4",
"@sanity/ui": "^0.38.0",
"react-copy-to-clipboard": "^5.1.0"
},

@@ -43,3 +43,3 @@ "peerDependencies": {

"@commitlint/config-conventional": "^15.0.0",
"@sanity/semantic-release-preset": "^1.1.3",
"@sanity/semantic-release-preset": "^2.0.1",
"@types/react": "^18.0.10",

@@ -46,0 +46,0 @@ "@types/react-copy-to-clipboard": "^5.0.2",

@@ -64,1 +64,12 @@ # @sanity/incompatible-plugin

If your v3 plugin gets installed in a V2 studio by mistake, a dialog will display how to fix it.
## Develop
### Release new version
Run ["CI & Release" workflow](https://github.com/sanity-io/incompatible-plugin/actions/workflows/main.yml).
Make sure to select the main branch and check "Release new version".
Semantic release will only release on configured branches, so it is safe to run release on any branch.
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc