New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing release of zone.js along with Angular 14.0.0 #46230
Comments
Hi @alxhub would you mind explaining why this issue was closed? |
@Platonn We intended to release |
A new angular version has just been released, but it's still missing the zone.js release (despite the merge of #46232 before the release of the new angular version), is it expected ? |
@Julien-Marcou No, this was a mistake. #46232 was just merged, and I think that @alxhub is releasing zone.js soon (correct me if I'm wrong) |
It is now available 👍 this issue can be closed 😄 |
Thank you @JiaLiPassion for cutting off the release branch and thank you folks for releasing |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Which @angular/* package(s) are the source of the bug
I wouldn’t call it a bug strictly, but those are the related packages:
@angular/core, zone.js
Is this a regression?
No
Description
Angular 14.0.0 Changelog mentions some changes in zone.js (related to this commit f19b36f), however new version of zone.js was not released yet.
By any chance, do you plan to release new zone.js@0.11.6 (or 0.12.0?) and point it as a peerDependency of angular/core@14.0.1?
If not, I think we should remove the zone.js changes from Angular 14 changelog.
cc @JiaLiPassion
Please provide a link to a minimal reproduction of the bug
N/A
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
I’m not sure if the issue template for bug is appropriate for this issue, but other templates like “feature request” or “docs” didn’t look more appropriate to me.
The text was updated successfully, but these errors were encountered: