Closed stianjensen closed 1 year ago
@ds300 @stianjensen is there any progress on this issue? I woke up this morning with a vulnerability report for semver 5.6 in my mailbox, it should be updated to 7.5.2
Please merge this.
Given this package declares itself to be node 14+, I don't think this change counts as needing a major semver from this PR ( it indicates that the versions dropped are so old that they can now use let
) - I'll get this merged and it can go out with the next release
@orta Thank you for merging this PR! Could you now publish a new version of patch-package
which has this fix in it?
@orta Is there an ETA on the next release?
@orta Can we please release a new version of the package?
I don't have npm access I'm afraid
sorry folks I'll do a release now
On Tue, Jul 11, 2023 at 8:47 AM Orta Therox @.***> wrote:
I don't have npm access I'm afraid
— Reply to this email directly, view it on GitHub https://github.com/ds300/patch-package/pull/466#issuecomment-1630322355, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJPLKIMNL6A7XXERBGG4HTXPUAJPANCNFSM6AAAAAAXM4YS3M . You are receiving this because you were mentioned.Message ID: @.***>
this jest went out in v7.0.1
https://github.com/npm/node-semver/blob/main/CHANGELOG.md
Major version change is mainly dropping old node versions.