@fastly/heroku-plugin
Advanced tools
Comparing version 2.0.1 to 2.0.2
@@ -0,1 +1,7 @@ | ||
## 2.0.2 | ||
### Changed | ||
- ⬆️ Fixed security problems in dependencies | ||
## 2.0.1 | ||
@@ -2,0 +8,0 @@ |
{ | ||
"name": "@fastly/heroku-plugin", | ||
"version": "2.0.1", | ||
"version": "2.0.2", | ||
"description": "Heroku CLI Plugin for interacting with Fastly CDN", | ||
@@ -5,0 +5,0 @@ "homepage": "https://www.fastly.com", |
@@ -16,3 +16,3 @@ # Heroku Fastly Plugin | ||
The CLI Plugin includes the commands: `tls`, `verify`, and `purge`. | ||
**** | ||
## TLS and Verify | ||
@@ -42,3 +42,3 @@ To add TLS to a domain your pricing plan must include a TLS domain and the domain must be configured in the active version of your Fastly Service. | ||
``` | ||
Checks the status of the verification process. If complete, a new CNAME will be output that you can update to after the new certificate propages to all caches. | ||
Checks the status of the verification process. If complete, a new CNAME will be output that you can update to after the new certificate propagates to all caches. | ||
@@ -83,4 +83,5 @@ | ||
* Clone this repo. | ||
* `cd` into `heroku-fastly` repo | ||
* Run `npm install`. | ||
* `cd` into `heroku-fastly` repo and run `heroku plugins:link`. | ||
* Run `heroku plugins:link`. | ||
* You can make sure this is working by running `heroku plugins`, will return something like: | ||
@@ -120,2 +121,12 @@ | ||
## Publishing | ||
- We follow [Semantic versioning](https://semver.org/) with regards to the | ||
version of this plugin. Any pull-requests to this project must include an | ||
appropriate change to the `package.json` file (as well as the | ||
`package-lock.json` file) and the `CHANGELOG.md` file. | ||
- After any PR has been merged, run an `npm publish` command from the `master` | ||
branch after pulling all changes in from `github`. | ||
## Contact us | ||
@@ -122,0 +133,0 @@ Have an issue? Please send an email to support@fastly.com. |
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
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
17697
135
0