What are the reasons that npm-publish@3.2.0 had to...
# npm-publish
a
What are the reasons that npm-publish@3.2.0 had to ditch all previous versions of kotlin??
b
Changes in kgp dependency resolution. You can still apply 3.2.0, but you won't get any dependencies resolved into package json.
Unfortunately npm-publish is hooking into unstable and undocumented KGP APIs to resolve dependencies, so until/if they're stabilised there's not much that can be done to avoid such upgrade limitations.
However if you don't mind listing out your npm dependencies manually, there's nothing else stopping you from upgrading with kotlin <1.8.
a
thanks for the clarification