-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
build: update to angular v9.0.6 #18785
build: update to angular v9.0.6 #18785
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Needs rebase |
64350e8
to
1ac5837
Compare
This comment has been minimized.
This comment has been minimized.
@googlebot Ping. |
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
PR is patch-only due to master being on the Angular beta for TS 3.8 right now. |
Uh, I think I broke your PR? Tried merging 9.1.x latest changes into your PR, now failing CI |
Updates to Angular v9.0.6. This version contains a fix for `@angular/bazel` that should fix the release output to not leak any Bazel runfile manifest paths. angular/angular@9581658
We recently updated `@octokit/rest`, but the most recent version currently has broken TypeScript definitions. To workaroun this until the upstream issue is resolved, we downgrade to our last working version. https://github.com/octokit/rest.js/issues/1624
Ensures that angular/angular@9581658 fixed all instances, and ensures that we don't regress on the components side.
d171ab0
to
c88a94c
Compare
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. |
Updates to Angular v9.0.6. This version contains a fix for
@angular/bazel
that should fix the release output to notleak any Bazel runfile manifest paths. angular/angular@9581658