http-status
Advanced tools
Comparing version 1.7.1 to 1.7.2
@@ -5,2 +5,4 @@ # Changelog | ||
### [1.7.2](https://github.com/adaltas/node-http-status/compare/v1.7.1...v1.7.2) (2023-10-17) | ||
### [1.7.1](https://github.com/adaltas/node-http-status/compare/v1.7.0...v1.7.1) (2023-10-17) | ||
@@ -7,0 +9,0 @@ |
{ | ||
"name": "http-status", | ||
"version": "1.7.1", | ||
"version": "1.7.2", | ||
"description": "Interact with HTTP status code", | ||
@@ -5,0 +5,0 @@ "homepage": "https://github.com/adaltas/node-http-status", |
@@ -197,11 +197,5 @@ [![Build Status](https://secure.travis-ci.org/adaltas/node-http-status.png)](http://travis-ci.org/adaltas/node-http-status) | ||
``` | ||
rm package-lock.json | ||
yarn run release | ||
git push --follow-tags origin master | ||
``` | ||
Package publication is handled by the CI/CD with GitHub action. | ||
Note: | ||
- On release, both the publish and test workflows run in parallel. Not very happy about it but I haven't found a better way. | ||
- `yarn` does not call the "postrelease" script and `npm` fails if the `package-lock.json` file is present and git ignored. |
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
70267
201