@govuk-pay/pay-js-commons - npm Package Compare versions

Comparing version 2.4.0 to 2.5.0

package.json

 {
   "name": "@govuk-pay/pay-js-commons",
-  "version": "2.4.0",
+  "version": "2.5.0",
   "description": "Reusable js scripts for GOV.UK Pay Node.js projects",
@@ -5,0 +5,0 @@ "main": "lib/index.js",

README.md

@@ -10,2 +10,3 @@ [![Build Status](https://travis-ci.org/alphagov/pay-js-commons.svg?branch=master)](https://travis-ci.org/alphagov/pay-js-commons)
 - [Nunjucks filters](#nunjucks-filters)
+- [Releasing a new version](#releasing-a-new-version)
 
@@ -170,1 +171,15 @@ ## Browsered scripts
 ```
+# Releasing a new version
+
+Versions are released to npm, to do so you need to be a member of https://www.npmjs.com/org/govuk-pay.
+
+Once you are a member run the following commands
+
+- make sure you are on the latest master version of `pay-js-commons`
+- `npm login` (if you’re not already logged in)
+- `npm version major|minor|patch` depending on which sort of release it is
+- `npm publish`
+
+Once you have done this it should be available instantly you can check by visiting https://www.npmjs.com/package/@govuk-pay/pay-js-commons and looking for your release, should say _published a few seconds ago_.
+
+Then you can go around our repos bumping the version in this [sort of fashion](https://github.com/alphagov/pay-frontend/pull/940).

New alerts

New author

Supply chain risk

A 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

Improved metrics

Total package byte prevSize

893857

increased by268.93%

Number of package files

55

increased by17.02%

Number of lines in readme file

184

increased by8.88%

Worsened metrics

Number of medium supply chain risk alerts

1

increased byInfinity%

No dependency changes