Skip to content

Conversation

@Trott
Copy link
Contributor

@Trott Trott commented Jan 29, 2022

This potentially fixes a security vulnerability in the dependency.
The breaking changes from 2.4.0 to 4.0.1 involved adoption of ES6
and dropping support for EOL Node.js versions. Neither should be a
problem here, I would expect.

Reference: GHSA-wpg7-2c88-r8xv

This potentially fixes a security vulnerability in the dependency.
The breaking changes from 2.4.0 to 4.0.1 involved adoption of ES6
and dropping support for EOL Node.js versions. Neither should be a
problem here, I would expect.

Reference: GHSA-wpg7-2c88-r8xv
@Trott
Copy link
Contributor Author

Trott commented Apr 6, 2022

I suppose this repo is inactive.

@Trott Trott closed this Apr 6, 2022
@chrisakroyd chrisakroyd reopened this Apr 11, 2022
@chrisakroyd
Copy link
Owner

Unfortunately GitHub had stopped sending me emails and notifications, I will check this out tomorrow but as all tests have passed it should be good to go. Thanks for this, and sorry for the delay.

@Trott
Copy link
Contributor Author

Trott commented Apr 12, 2022

Coverage change doesn't seem related, does it?

@chrisakroyd chrisakroyd merged commit 9800e12 into chrisakroyd:master May 6, 2022
@chrisakroyd
Copy link
Owner

I can't work out what's caused the coverage dip, will spend some time figuring it out. Merged and published, thanks for the commit and it should be on npm as version 2.0.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants