gatsby-plugin-newrelic 2.2.1 → 2.2.2

package/CONTRIBUTING.md

@@ -22,7 +22,7 @@ Before submitting an Issue, please search for similar ones in the
 
  A [Github workflow](https://github.com/newrelic/gatsby-plugin-newrelic/blob/main/.github/workflows/release.yml) which uses NPX [semantic-release](https://semantic-release.gitbook.io/semantic-release/usage/configuration#branches) exists to assist in publishing next versions of this plugin to NPM.
 
- > If you wish to publish a next version to NPM follow these steps.
+ > If you wish to publish a latest version to NPM follow these steps but ensure you change the tag in [package.json](package.json) to latest
 
  1. Make your changes on a local branch from main.
  2. After pulling down the code, run `git fetch && git pull` to ensure you have the latest code for main.

package/docs/CHANGELOG.md

@@ -1,3 +1,10 @@
+## [2.2.2](https://github.com/newrelic/gatsby-plugin-newrelic/compare/v2.2.1...v2.2.2) (2022-02-09)
+
+
+### Bug Fixes
+
+* publishes a latest version ([c2e68bb](https://github.com/newrelic/gatsby-plugin-newrelic/commit/c2e68bbe191c1ee4ea7657ecd44f953bc7213a2b))
+
 ## [2.2.1](https://github.com/newrelic/gatsby-plugin-newrelic/compare/v2.2.0...v2.2.1) (2022-02-08)
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gatsby-plugin-newrelic",
-  "version": "2.2.1",
+  "version": "2.2.2",
   "description": "Gatsby plugin for implementing the New Relic Browser agent",
   "main": "index.js",
   "scripts": {
@@ -47,6 +47,6 @@
   "private": false,
   "publishConfig": {
     "registry": "https://registry.npmjs.org/",
-    "tag": "next"
+    "tag": "latest"
   }
 }