the major update to rsa-compat should have caused a major version update to greenlock #36
Label
Kein Label
Kein Meilenstein
Niemand zuständig
2 Beteiligte
Nachrichten
Fällig am
Kein Fälligkeitsdatum gesetzt.
Abhängigkeiten
Keine Abhängigkeiten gesetzt.
Referenz: coolaj86/greenlock.js-ARCHIVED#36
Laden…
In neuem Issue referenzieren
Keine Beschreibung angegeben.
Branch "%!s(<nil>)" löschen
Das Löschen eines Branches ist permanent. Obwohl der Branch für eine kurze Zeit weiter existieren könnte, kann diese Aktion in den meisten Fällen NICHT rückgängig gemacht werden. Fortfahren?
in v2.6.8 of greenlock, rsa-compat was updated to v2.0.3 from v1.9.2, which is a breaking change. it might have been better to bump greenlock to v3 to signal the breaking change. Our app broke since we are currently on node v8.
Can you tell me what broke so I can fix it?
As far as I know there were no breaking changes.
The external dependencies were made explicit and that was it. Everything should still work with node v8.
our app used to work without the need for
ursa. after a deployment it broke here. we found thatursais now required for our app to work since we are on node < 10.there is nothing specifically broken now but this hiccup may have been avoided if greenlock had a major version upgrade.