fix: remove invalid engines field
https://github.com/jshttp/content-disposition/pull/77#pullrequestreview-2804731439
cc: @UlisesGascon @blakeembrey
@bjohansebas We have to options for the next release. Remove the emgines field and release v1.0.1 or publish v2
@Phillip9587 @blakeembrey This PR would go against what this ADR proposes (https://github.com/expressjs/discussions/pull/289)
@bjohansebas it was noted in the comment by @wesleytodd but I’ve added a review to clarify it in the ADR since it seems to be confusing:
The only thing I think is missing is the call-out that all more restrictive engines changes can only land with a MAJOR. And that we agreed major versions should not be cut just to change node support.
I will bring this to the next TC meeting https://github.com/expressjs/discussions/issues/370 and see if we need an exception to the ADR policy to land this on 1.0.1 :crossed_fingers:
@UlisesGascon Has there been a decision from the TC?