Repository navigation
Conversation
|
Nice! |
There was a problem hiding this comment.
Haha, nice one but still incorrect :)
|
Just an FYI.. you have 2.10 in a few spots here. The next version is actually 3.0. |
|
@IgorMinar what's the status of this? We'd like to move google3 to TS2.9 and are blocked on this. |
|
Since @IgorMinar is on vacation, I will take over this PR. |
|
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) |
|
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) |
|
Blocked on angular/tsickle#846 |
|
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) |
|
You can preview e601954 at https://pr24652-e601954.ngbuilds.io/. |
|
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
|
You can preview fd69070 at https://pr24652-fd69070.ngbuilds.io/. |
|
You can preview 5331d1b at https://pr24652-5331d1b.ngbuilds.io/. |
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) |
| "@angular/upgrade": "file:../../dist/packages-dist/upgrade", | ||
| "@types/jasmine": "2.5.41", | ||
| "rxjs": "file:../../node_modules/rxjs", | ||
| "typescript": "2.8.x", |
There was a problem hiding this comment.
@mhevery Is it not weird to have 2.8.x in the package.json of typings_test_ts29. Shouldn't that be 2.9.x (and in the description above)
There was a problem hiding this comment.
good catch, and thanks for the fix.
|
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. |
known issues:
I haven't investigated this yet.- the issue identified with a runtime error due to undefined "selector" property seems to be a breakage in the master/HEAD and unrelated to my change.