This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of typescript.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 4470 commits (ahead by 4470, behind by 81).
Coverage remained the same at 99.324% when pulling 10f12f81184f6e90d19f84157651dd433d251374 on greenkeeper-typescript-2.0.3 into 0761d38da2290fd1d3b710ceb86b1bd5379cd176 on master.
Coverage remained the same at 99.324% when pulling 10f12f81184f6e90d19f84157651dd433d251374 on greenkeeper-typescript-2.0.3 into 0761d38da2290fd1d3b710ceb86b1bd5379cd176 on master.
Coverage remained the same at 99.324% when pulling 10f12f81184f6e90d19f84157651dd433d251374 on greenkeeper-typescript-2.0.3 into 0761d38da2290fd1d3b710ceb86b1bd5379cd176 on master.
Coverage remained the same at 99.324% when pulling 10f12f81184f6e90d19f84157651dd433d251374 on greenkeeper-typescript-2.0.3 into 0761d38da2290fd1d3b710ceb86b1bd5379cd176 on master.
Hello lovely humans,
typescript just published its new version 2.0.3.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of typescript. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 4470 commits (ahead by 4470, behind by 81).
4f65a28
Update LKG
3a46371
Add back getSourceFile and mark it as deprecated
5f1336b
Update LKG
c98103b
Merge pull request #10928 from Microsoft/addTestFix10625
bca3493
Merge pull request #10930 from RyanCavanaugh/release-2.0
d37391f
Allow type and NS references to UMD globals from modules
48e51b5
Add tests and baselines
4ce2280
Update LKG
93e0451
Merge branch 'release-2.0_fix10625' into release-2.0
9cabffe
Merge branch 'release-2.0' into release-2.0_fix10625
0c443c2
Update LKG
14b59b2
Address PR
b6aeaab
Update version
ced8cf8
Add tests and update baselines
332b316
Emit declaration file which inferred type alias with its value
There are 250 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade