gatsby-plugin-newrelic 2.0.2 → 2.1.1

package/.github/workflows/release.yml

@@ -49,7 +49,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v1
         with:
-          node-version: 10.x
+          node-version: 16.x
 
       - name: Cache node_modules
         id: cache-node-modules
@@ -90,7 +90,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v1
         with:
-          node-version: 10.x
+          node-version: 16.x
 
       - name: Download Cached Deps
         id: cache-node-modules
@@ -211,7 +211,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v1
         with:
-          node-version: 10.x
+          node-version: 16.x
 
       - name: Download Cached Deps
         id: cache-node-modules

package/CONTRIBUTING.md

@@ -18,6 +18,19 @@ Before submitting an Issue, please search for similar ones in the
 2. Increase the version numbers in any examples files and the README.md to the new version that this Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
 3. You may merge the Pull Request in once you have the sign-off of two other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you.
 
+## Publishing next versions to NPM
+
+ 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.
+
+ 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.
+ 3. Commit your changes and submit a PR to the `next` branch.
+ 4. Ensure that you [bump the version of the package](https://cloudfour.com/thinks/how-to-publish-an-updated-version-of-an-npm-package/#the-standard-release-process) by using semantic versioning using the `NPM version` command.
+ 5. This will kick off the workflow to publish a next version to NPM.
+ 6. Go to [NPM](https://www.npmjs.com/package/gatsby-plugin-newrelic) to view the next branch.
+
 ## Contributor License Agreement
 
 Keep in mind that when you submit your Pull Request, you'll need to sign the CLA via the click-through using CLA-Assistant. If you'd like to execute our corporate CLA, or if you have any questions, please drop us an email at opensource@newrelic.com.

package/README.md

@@ -8,12 +8,12 @@ The New Relic Gatsby Plugin provides a simple to use configuration option for in
 
 ## Installation
 
-1. If you don't already have a New Relic account, [sign-up for our free forever tier - no credit-card required!](https://newrelic.com/signup)
-1. Go to [https://rpm.newrelic.com](https://rpm.newrelic.com)
-1. Select the "Browser" product from the navigation
-1. Click on "Add more" to add your website
+1. If you don't already have a New Relic account, [sign-up for our free forever tier - no credit-card required!](https://trynewrelic.com/gatsby)
+1. Go to [https://one.newrelic.com](https://one.newrelic.com)
+1. Click on "Add more data" to add your website
+1. In the "Browser metrics" section, select "New Relic Browser"
 1. Select "Copy/Paste Javascript code" and copy the code
-1. Under "Choose your instrumentation" select Lite, Pro, or Pro + SPA
+1. Follow the steps to configure your instrumentation
 1. Enter your app name
 1. Click "Enable"
 1. Paste the JS snippet provided into a text editor
@@ -87,7 +87,6 @@ The New Relic Gatsby Plugin provides a simple to use configuration option for in
     }
     ```
 
-    Note - `instrumentationType` can be `lite`, `pro`, `proAndSPA`, corresponding with levels of our browser agent.
 
 1. Set the `GATSBY_NEWRELIC_ENV` to point at the appropriate config. For local dev you would add `GATSBY_NEWRELIC_ENV=dev` to the front of your "develop" script in your project's `package.json`. For "production" you would add `GATSBY_NEWRELIC_ENV=production` to the front of the Gatsby "build" command.
     Ex. `package.json`:

package/docs/CHANGELOG.md

@@ -1,3 +1,23 @@
+## [2.1.1](https://github.com/newrelic/gatsby-plugin-newrelic/compare/v2.1.0...v2.1.1) (2022-01-10)
+
+
+### Bug Fixes
+
+* updated contributing guide ([af6aa1c](https://github.com/newrelic/gatsby-plugin-newrelic/commit/af6aa1c48603a36641099b7ab6c2612e31fa11bc))
+
+# [2.1.0](https://github.com/newrelic/gatsby-plugin-newrelic/compare/v2.0.2...v2.1.0) (2022-01-06)
+
+
+### Bug Fixes
+
+* bumped the node version ([bc7f7ee](https://github.com/newrelic/gatsby-plugin-newrelic/commit/bc7f7ee43f68a07a6381fded83195786783399a6))
+* update ci node version ([7fec128](https://github.com/newrelic/gatsby-plugin-newrelic/commit/7fec128c63852a78f8be23a3bb06cb65c7322c65))
+
+
+### Features
+
+* adds support for gatsby 4 ([a7b5ba3](https://github.com/newrelic/gatsby-plugin-newrelic/commit/a7b5ba3c21aa772e7c300af167f894cf5019dd45))
+
 ## [2.0.2](https://github.com/newrelic/gatsby-plugin-newrelic/compare/v2.0.1...v2.0.2) (2021-08-06)
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gatsby-plugin-newrelic",
-  "version": "2.0.2",
+  "version": "2.1.1",
   "description": "Gatsby plugin for implementing the New Relic Browser agent",
   "main": "index.js",
   "scripts": {
@@ -19,7 +19,7 @@
   },
   "homepage": "https://opensource.newrelic.com/projects/newrelic/gatsby-plugin-newrelic",
   "peerDependencies": {
-    "gatsby": "^3.0.0",
+    "gatsby": "3.x || 4.x",
     "react": "^17.0.0",
     "react-dom": "^17.0.0"
   },
@@ -42,11 +42,11 @@
     "cross-env": "^5.2.1"
   },
   "engines": {
-    "node": ">=10.13.0"
+    "node": ">=16.3.1"
   },
   "private": false,
   "publishConfig": {
     "registry": "https://registry.npmjs.org/",
-    "tag": "latest"
+    "tag": "next"
   }
 }