An in-range update of alsatian is breaking the build π¨
Opened this issue Β· 0 comments
greenkeeper commented
Version 1.3.1 of alsatian just got published.
Branch | Build failing π¨ |
---|---|
Dependency | alsatian |
Current Version | 1.3.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As alsatian is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you itβs very likely also breaking them.
I recommend you give this issue a very high priority. Iβm sure you can resolve this πͺ
Status Details
Commits
The new version differs by 32 commits .
085a87e
release 1.3.1
e7bbb28
Merge pull request #350 from jamesrichford/issue#344
47f30c7
cast to any to check error correctly
8d2cb1e
update integration test build
6550136
update object type to TypeScript 2.2 type
0e1e2ad
add install-self to deps
b04fe34
tidy up compile spec
179ab7d
Merge branch 'issue#344' of https://github.com/jamesrichford/alsatian into issue#344
1aa4267
break up long line
c9e7133
Merge branch 'master' into issue#344
758ebcc
disabling typescript tests until bundling
e3759f2
get some debug on
25e6ad9
add integration tests
b6090a2
update method decorator signatures
3bea50c
Merge pull request #328 from alsatian-test/greenkeeper/@types/selenium-webdriver-3.0.0
There are 32 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 π΄