@graphcms/validation
Advanced tools
Comparing version 1.3.18 to 1.3.19
{ | ||
"name": "@graphcms/validation", | ||
"version": "1.3.18", | ||
"version": "1.3.19", | ||
"main": "dist/validation.js", | ||
@@ -36,5 +36,9 @@ "types": "dist/index.d.ts", | ||
"build": "microbundle --target browser --compress false", | ||
"dev": "microbundle watch" | ||
"dev": "microbundle watch", | ||
"changeset": "changeset", | ||
"release": "changeset publish" | ||
}, | ||
"devDependencies": { | ||
"@changesets/changelog-github": "^0.4.1", | ||
"@changesets/cli": "^2.17.0", | ||
"@types/jest": "^23.3.8", | ||
@@ -41,0 +45,0 @@ "@types/yup": "^0.26.0", |
@@ -6,2 +6,11 @@ # GraphCMS/validation | ||
## Publishing to npm | ||
Publishing is automated using [Changesets](https://github.com/atlassian/changesets): | ||
On your feature branch when your are done with your changes, run `yarn changeset` to generate a changeset file, | ||
which will include a short desciption of the change and the generated version bump. | ||
Commit the generated file, push, and open a PR. Check that the changeset is detected accordingly by github in the PR. | ||
Once the PR gets merged to master, the changset will be applied and the package released to npm. | ||
## Usage | ||
@@ -8,0 +17,0 @@ Let's say you want to check if some string is a valid model api id. |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
1311
67
181047
12
117