the major update to rsa-compat should have caused a major version update to greenlock #36
Etiķetes
Nav etiķešu
Nav atskaites punktu
Nav atbildīgo
2 dalībnieki
Paziņojumi
Izpildes termiņš
Izpildes termiņš nav uzstādīts.
Atkarības
Nav atkarību.
Atsaucas uz: coolaj86/greenlock.js-ARCHIVED#36
Notiek ielāde…
Atsaukties uz šo jaunā problēmā
No description provided.
Dzēst atzaru "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.