v2.0.0

What's Changed

• breaking: Remove support for Node 14 by @Nevon in #432
• Replace spected with zod by @Nevon in #433
• Bump ansi-regex from 5.0.0 to 5.0.1 by @dependabot in #434
• v2.0.0 by @Nevon in #435

Full Changelog: v1.0.3...v2.0.0

v1.0.3

What's Changed

• Support for Node >= 18

v1.0.2

• Updated dependencies to fix vulnerabilities

v1.0.1

What's Changed

• Updated dependencies to fix vulnerabilities #406 #412

Full Changelog: v1.0.0...v1.0.1

Improved healthcheck response error messaging

See #7.

Previously when you created a healthcheck response object that was not according to the schema, an InvalidHealthcheckResponse error would get thrown, but the message provided in the error was very generic and unhelpful, so figuring out what you did wrong would require you to read the readme to try to figure out what you were doing wrong.

Now, the message of the error will tell you exactly what you did wrong, so that it will hopefully be much easier to debug an invalid healthcheck response!

Update dependencies and implement InvalidHealthcheckResponse error

physical.response will now return an InvalidHealthcheckResponse error if called with invalid parameters.

Automatic schema validation

• The response producted by the middleware is now automatically verified against a swagger definition.
• DEPRECATION physical.severities.WARN is now deprecated in favor of physical.severities.WARNING
• Both healthy and unhealthy will be included in the response, even if they are empty.

dependentOn required for healthy checks

v0.2.0

0.2.0

500 on failing checks

When any check is failing, the middleware will now respond with a status code of 500.