@clearkit/one
Advanced tools
Comparing version 1.2.4-11 to 1.2.4
{ | ||
"name": "@clearkit/one", | ||
"version": "1.2.4-11", | ||
"version": "1.2.4", | ||
"description": "ClearKit One", | ||
@@ -11,3 +11,2 @@ "main": "config/index.js", | ||
"config", | ||
"lib", | ||
"src", | ||
@@ -30,3 +29,2 @@ "dist" | ||
"next": "^12.1.6", | ||
"np": "^7.6.1", | ||
"npm-run-all": "^4.1.5", | ||
@@ -57,3 +55,2 @@ "postcss": "^7", | ||
"postcss:build:components": "postcss src/css/components.css -o dist/components.css", | ||
"release": "yarn build && np", | ||
"start": "npm-run-all -s clean -p docs:dev" | ||
@@ -65,3 +62,3 @@ }, | ||
}, | ||
"author": "@dizzyup @mginnard @mattrothenberg", | ||
"author": "@dizzyup @mginnard @mattrothenberg @zsteiner", | ||
"license": "ISC", | ||
@@ -68,0 +65,0 @@ "bugs": { |
@@ -39,4 +39,2 @@ # ClearKit One | ||
Voilà! | ||
## Local Development | ||
@@ -49,19 +47,6 @@ | ||
## Publishing New Versions | ||
## Publish New Versions | ||
We use the tool [`np`](https://github.com/sindresorhus/np) (installed globally) for deploying new versions of the library. There's no need to change the package version in `package.json` as `np` will handle incrementing the version when publishing. | ||
This repo uses GitHub actions to automate releases and publishing. There is no need to manually create tags, releases, or publish to npm. | ||
When you're ready to deploy and your changes BUT BEFORE THEY are pushed to master, run `yarn release` and it will walk you through the steps: | ||
- Verifying tests pass | ||
- Choosing a new version number | ||
- Auto-tagging and release notes | ||
- Publishing to NPM | ||
```bash | ||
np --no-tests | ||
``` | ||
After publishing and comitting bumped version in package.json, you can merge and delete pull request. | ||
You may need to run `npm login` and `yarn login`. Make sure to have your authenticator app handy for OTP for npm. | ||
Follow the [instructions for using actions](https://github.com/clearbit/github-actions#publish--release) when creating pull requests. Take careful note of how to use labels to create semantic versions. |
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
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
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
26
1
6231907
11548
51