Closed dbutenhof closed 1 year ago
Ugh. How are we going to know (and remember) to back this out again?
Yeah; it's an issue, but there's already a keycloak-js
PR to fix it, so with luck we can repair this later today.
Apparently what happened was adding explicit versions to all dependencies; and keycloak-masthead
is an internal package that's not actually published separately. Their CI must only use a contaminated node_modules
cache; but the version makes npm
try to fetch it, which can't ever work because it's not published. Yikes.
keycloak-js
21.1.0 adds an explicitkeycloak-masthead
dependency that's broken. This went in early this morning, and has broken all users. To mitigate this, back off ourpackage.json
to depend on the latest previous verion, which is 21.0.2 to get our builds running again.