v8.0.0: Upgrade node-fetch ^1.5.1 -> ^2.6.7

What's Changed

• Upgrades node-fetch dependency from v1 -> v2 (see #204 for more details)

v7.0.2: Add Heroku log drain host format check

Includes:

• Add Heroku log drain host format check
• Fix unusable Markdown in Heroku log drain check panic guide text

v7.0.1: Modify Heroku log drain check to ensure absence of sourcetype param

For details see PR #201: Modify Heroku log drain check to ensure absence of sourcetype param

Heroku log drains weren't quite ready when we originally made its healthchecks, and so don't match the final requirements of the Heroku log drain endpoint (i.e. not sending a sourcetype param). Therefore this is a fix to make our tooling compatible and so is a patch release.

v7.0.0

Breaking Changes

This release removes n-raven as a dependency, which means that broken health checks no longer get logged to Sentry. This is considered a breaking change because application logs/metrics are part of the API (you may see fewer Sentry logs), but there are no breaking changes to the JavaScript API of this library.

What's Changed

• Fix the codeowners file by @rowanmanning in #198
• Remove n-raven by @rowanmanning in #199

Full Changelog: v6.3.0...v7.0.0

v6.3.0

What's Changed

• Add a Heroku log drain check type by @rowanmanning in #197

Full Changelog: v6.2.0...v6.3.0

v6.2.0

What's Changed

• Temporarily add Dotcom Support as co-owners by @rowanmanning in #195
• Require n-logger v10.2.0 by @rowanmanning in #196 (adding the ability to switch to Heroku log drains)

New Contributors

• @rowanmanning made their first contribution in #195

Full Changelog: v6.1.2...v6.2.0

v6.1.2

What's Changed

• FTDCS-196 - Comply with the standards by @JSRedondo in #193
• [Snyk] Security upgrade moment from 2.29.3 to 2.29.4 by @jamesr101 in #194

New Contributors

• @jamesr101 made their first contribution in #194

Full Changelog: v6.1.1...v6.1.2

Fix for FastlyKeyExpirationCheck default properties

What's Changed

• FTDCS-196 - Fix health check FastlyKeyExpirationCheck by @JSRedondo in #192

Full Changelog: v6.1.0...v6.1.1

Add Fastly key expiration check

At the moment our Fastly keys are unmanageable - they’re stored in individual user accounts in Fastly and we cannot enforce things like key expiry or rotation.
We should add a check type to n-health which verifies Fastly keys using https://api.fastly.com/tokens/self:

• alert if the key expires in the next week or two
• alert if the key has a null expiry date

What's Changed

• FTDCS-152 - Fix CircleCI configuration file by @JSRedondo in #185
• FTDCS-152 - Update moment package to solve a vulnerability by @JSRedondo in #184
• CPP-890 update config for nightly scheduled-pipelines by @serena97 in #186
• FTDCS-196 - Update testing by @JSRedondo in #187
• FTDCS-196 - Fastly key expiration check merge by @JSRedondo in #189
• FTDCS-196 - Improve Fastly key expiration check by @JSRedondo in #190
• FTDCS-196 - Added default panic guide for Fastly key expiration check by @JSRedondo in #191

New Contributors

• @JSRedondo made their first contribution in #185

Full Changelog: v6.0.0...v6.1.0

Migrate to Node 14 + 16

What's Changed

• Add npm-publish-token CircleCI context by @serena97 in #175
• Add support for Node 14 and Node 16 by @ivomurrell in #174

Breaking Changes

• Dropped support for Node 12

Full Changelog: v5.0.6...v6.0.0