Razzle: Canary release publishing to npm is broken

[pauliusuza]

Canary Releases are Broken

Would it be possible to unblock Canary publishing to NPM❓
Thanks

[fivethreeo]

Working on it.

[fivethreeo]

But stuck, may be just the npm token.

[pauliusuza]

Thanks a lot for quick reaction!

[fivethreeo]

When you say broken, do you publish it to a local repo and that does not work. Or are you asserting that it does not work for us?

[pauliusuza]

I mean that the latest canary version available on npm is .47, publishing action fails for quite some time: https://github.com/jaredpalmer/razzle/actions/runs/595988963

[fivethreeo]

Ah, was not sure who could see actions. That explains my confusion. Waiting for Jared to add a new token.... to see if that fixes it.

[fivethreeo]

Fixed :)

[pauliusuza]

Thanks! I assume the new v4.0.0-canary.50 is the same as the unpublished v4.0.0-canary.84?

[fivethreeo]

Yes

On Thu, 25 Feb 2021 at 17:02, Paulius Uza [e-mail] wrote:

Thanks! I assume the new v4.0.0-canary.50 is the same as the unpublished
v4.0.0-canary.84?

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/jaredpalmer/razzle/issues/1563#issuecomment-786010166,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAADGVCKD2JEI5JNDVL73TTAZYALANCNFSM4YFNCD7Q
.

--
Øyvind Saltvik