v9.1.2 not published to npm yet

[bmarcotte]

Looks like the tag for v9.1.2 was created two days ago, but that version has not been published to npm yet, and it still shows 9.1.1 as the latest version. So, at the moment, the latest version of @angular/cli is lagging behind the rest of the recently published @angular packages.

Is there a particular issue holding up publishing v9.1.2? Or was this just an oversight?

[alan-agius4]

Hi @bmarcotte, we are of aware of that.

@dgp1130 is working on the release.

[dgp1130]

Yes I'm working on the release. CI is being difficult this time, hopefully I'll get it out today.

[dgp1130]

I was able to get a green CI. Though I'm not able to publish right now due to some issues with Wombat. At this point, it's too late on a Friday that I don't want to do the release anyways. I'd rather not risk problems over the weekend. I handed off caretaking to @kyliau who can follow up with this on Monday.

[EatonZ]

Hi, is this still planned for today?

[bmarcotte]

While we're waiting for any news on this release, perhaps the team can tell us what they suggest: When @angular/core and @angular/cli get out of sync like this, which of the following do you recommend?

1. Don't update @angular/core until there's a corresponding @angular/cli version to go with it.
2. Go ahead and update @angular/core, and don't worry about them being out of sync.

[alan-agius4]

Hi all,

It's perfectly fine and safe to use different patch versions of CLI and Framework.

[kyliau]

version 9.1.2 has been published, as well as the next version 10.0.0-next.1
I apologize for the delay, we've been having some issues with this release because we transitioned from the default NPM registry to a Google proxy for security reasons and it hasn't worked as anticipated.