-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.3.7 has a breaking change #160
Comments
See Automattic/cli-table#160 for the breaking change that necessitates pinning `cli-table`
I guess we won't make any further changes to 0.3.x line. Node and packages it supports are too old and discontinued, and so should 0.3.x be marked as: old and discontinued. |
That’s a reasonable position to take, but v0.3.7 still need to be capped off with a v0.3 release that restores old node support. |
A perhaps easy alternative is republishing v0.3.6 as v0.3.latest, and then publishing the actual latest as v0.4.0? |
That's exactly what I am doing. |
Released v0.3.10 which reverts all changes to v0.3.6. |
@chrean thanks for looking into this.
|
Thanks! https://unpkg.com/[email protected]/package.json seems like it should work fine; I’ll try to revert the pinning in tbranyen/salita@68abf80 later today and confirm. |
@michaelarnauts is right. Going to fix it. |
0.3.11 is out, I have deleted all references to |
No worries, you are doing awesome work! |
v0.3.7 has a breaking change - it adds strip-ansi v6, which breaks support for node < 12.
This should have been v0.4.0 instead, since v0.3.6 declares an
engines
of{ node: '>= 0.2.0' }
. Also, changing "engines" to make previously valid things invalid is also a breaking change, which v0.3.7 did as well.Can you please publish a v0.3.x version that reverts that change, and then feel free to republish v0.4.0 with the breaking change?
The text was updated successfully, but these errors were encountered: