v10.0.0

What's Changed

• Remove snyk [automated] by @rowanmanning in #140
• Drop Node.js 16 support by @rowanmanning in #141
• Bump ip from 2.0.0 to 2.0.1 by @dependabot in #139

New Contributors

• @dependabot made their first contribution in #139

Full Changelog: v9.1.0...v10.0.0

v9.1.0

What's Changed

• Add support for Node.js 20 by @rowanmanning in #138

Full Changelog: v9.0.1...v9.1.0

v9.0.1

What's Changed

• Update dependencies by @rowanmanning in #133

Full Changelog: v9.0.0...v9.0.1

v9.0.0

What's Changed

• Breaking: replace n-logger with Reliability Kit logger by @rowanmanning in #130

Full Changelog: v8.1.0...v9.0.0

v8.1.0 - Add support for Node 18

What's Changed

• Upgrade Node 18 by @ivomurrell in #128

Full Changelog: v8.0.0...v8.1.0

v8.0.0

This release is part of the Platforms and Reliability set of scheduled breaking change releases in April.

The breaking changes in this package release are:

• Dropping support for Node.js 14

This will not be a breaking change for your application if it:

• Already runs on Node.js 16

If this is a breaking change for your application because it does not yet run on Node 16 you can follow this guide to migrate from Node.js 14 to Node.js 16

v7.2.2

Tool Kit migration. No functional change but release is being created to test the release process works successfully.

What's Changed

• CP-1008: Tool kit migration by @jkerr321 in #110

New Contributors

• @jkerr321 made their first contribution in #110

Full Changelog: v7.2.1...v7.2.2

v7.2.1

What's Changed

• Move mockery to devDependencies by @alexmuller in #103

Full Changelog: v7.2.0...v7.2.1

v7.2.0: Log poller state issues

What's Changed

• Update CODEOWNERS to the new team name by @rowanmanning in #97
• Don't throw errors and log poller state issues by @rowanmanning in #98

N.B. This removes any breaking changes for v7, i.e. you can perform a major upgrade from a v6 to v7 without any breaking changes.

New Contributors

• @rowanmanning made their first contribution in #97

Full Changelog: v6.1.0...v7.2.0

v7.1.1: Empty release to publish v7 with 'latest' tag

A maintenance release (v6.1.x) was issued, meaning it became tagged as the latest version of the package when that should be v7.

This is an empty release to ensure that v7 is correctly tagged with latest.