Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

http-status

Package Overview
Dependencies
Maintainers
1
Versions
42
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

http-status - npm Package Compare versions

Comparing version 1.7.1 to 1.7.2

2

CHANGELOG.md

@@ -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 @@

2

package.json
{
"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.
SocketSocket SOC 2 Logo

Product

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

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc