Update alsatian to the latest version 🚀 #7
Conversation
This file contains 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
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Version 2.1.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 72 commits.
There are 72 commits in total. See the full diff |
Version 2.2.1 just got published. |
Version 2.3.0 just got published. |
|
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.
Version 2.0.0 of alsatian just got published.
The version 2.0.0 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 alsatian.
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.
Commits
The new version differs by 161 commits ahead by 161, behind by 3.
2185c53Merge pull request #406 from jamesrichford/issue-375936bef9add tests for zero padding cachef7f2b30Merge branch 'issue-375' of https://github.com/jamesrichford/alsatian into issue-3753a0e060remove test focuscb2d4c1Merge branch 'master' into issue-37587c3b84ensure publishing only happens under one job45c4706split travis build by build type438b938Merge pull request #402 from winksaville/Stricter-tsc-options-2ba9d7beStricter-tsc-options-2354f52cMerge pull request #399 from jamesrichford/issue-388b78ac12remove trailing whitespace7727479Merge branch 'master' into issue-38889ef9abMerge pull request #400 from jamesrichford/issue-38010e19ccadd newline at end of filef8a9f66resolve lintingThere are 161 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴