Update typescript to version 2.1.6 🚀 #29
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Coverage remained the same at 99.507% when pulling c649dce879ad0fa600c8d25d3c72874891f82e08 on greenkeeper-typescript-2.1.6 into a6a3ad3 on master. |
mseemann
force-pushed
the
greenkeeper-typescript-2.1.6
branch
from
c649dce to
46cbe6d
Compare
|
Coverage remained the same at 99.507% when pulling 46cbe6d5c53e00f9fa56612cb6b65b260cda656e on greenkeeper-typescript-2.1.6 into 8e15bb8 on master. |
mseemann
force-pushed
the
greenkeeper-typescript-2.1.6
branch
from
46cbe6d to
653a927
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
typescript just published its new version 2.1.6.
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 ✨
You rock!
🌴
The new version differs by 263 commits .
496e7abMerge pull request #13945 from Microsoft/upateLKGrelease-2.1064a997Update LKG54220a8Merge pull request #13943 from Microsoft/runtestsd99901fDo not run npm updatedb30899Merge pull request #13938 from Microsoft/vladima/port-13937504e143Update versionba81c6cdisable fs watcher for UNC paths on Windows (#13937)b611dceMerge pull request #13824 from Microsoft/billti/updateLKG3b54f29Update LKG870e44fMerge pull request #13818 from Microsoft/release-2.1_atad5f5d78Use "ts2.1" NPM tag in typingsInstaller2dbc531Update LKGc26f402Merge pull request #13277 from Microsoft/fix13276f412e10Fix the emit when jsx attribute expression is empty32cec58Update LKGThere are 250 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.