Hello,
Running npm exec -- ctrf with ctrf@0.2.1 prints this warning:
⚠️ DEPRECATION NOTICE: This CLI is deprecated and will be removed in v1.
📦 Please use the standalone ctrf-cli package instead.
However, ctrf-cli@0.0.5 declares ctrf as ^0.1.0. This resolves to ctrf@0.1.0.
I considered overriding the transitive dependency to ctrf@0.2.1. That would require maintaining the version manually because Dependabot does not reliably handle dependencies constrained by overrides.
This leaves the following options:
- Use
ctrf-cli with ctrf@0.1.0.
- Add an override and maintain the overridden version manually.
- Use the deprecated CLI from
ctrf@0.2.1, accept the warning, and lack commands such as validate.
Could you publish a new ctrf-cli release that pins its ctrf dependency to the current compatible version?
Could future ctrf-cli releases be published alongside ctrf releases when CLI compatibility changes?
Hello,
Running
npm exec -- ctrfwithctrf@0.2.1prints this warning:However,
ctrf-cli@0.0.5declaresctrfas^0.1.0. This resolves toctrf@0.1.0.I considered overriding the transitive dependency to
ctrf@0.2.1. That would require maintaining the version manually because Dependabot does not reliably handle dependencies constrained byoverrides.This leaves the following options:
ctrf-cliwithctrf@0.1.0.ctrf@0.2.1, accept the warning, and lack commands such asvalidate.Could you publish a new
ctrf-clirelease that pins itsctrfdependency to the current compatible version?Could future
ctrf-clireleases be published alongsidectrfreleases when CLI compatibility changes?