You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#250 removed the dependency on byline and added json-stream. This change was part of all releases starting 0.9.0, including part of the latest release to date, 0.10.2.
However, 57f6c0b switched back from json-stream to byline, and since there is no release that contains this change, dependents that used byline who are updating this package from before 0.9 experience failure due to the missing package.
A new release based off mastershould mitigate this, and a workaround is to directly add "byline": "^5.0.0" as a dependency.
The text was updated successfully, but these errors were encountered:
@radu-matei I am a little confused is your application is dependant on byline and upgrading to 0.10.2 broke because we removed byline and you were explicitly using it somewhere?
Precisely - that being said, we should probably have explicitly declared it as a dependency (and did after upgrading the Kubernetes client, so this is not blocking in any way) - that being said, a new release would ensure that this doesn't break future upgrades from older versions that relied on byline.
I'm going to close this. We're going to do a new release eventually, but I don't think that there's anything actionable other than "do a new release" which we will definitely get to eventually....
#250 removed the dependency on
byline
and addedjson-stream
. This change was part of all releases starting 0.9.0, including part of the latest release to date, 0.10.2.However, 57f6c0b switched back from
json-stream
tobyline
, and since there is no release that contains this change, dependents that usedbyline
who are updating this package from before 0.9 experience failure due to the missing package.A new release based off
master
should mitigate this, and a workaround is to directly add"byline": "^5.0.0"
as a dependency.The text was updated successfully, but these errors were encountered: