Open greenkeeper[bot] opened 7 years ago
Your tests are passing again with this version. Explicitly upgrade to this version 🚀
<a name"3.2.3">
Your tests are passing again with this version. Explicitly upgrade to this version 🚀
<a name"3.2.4">
The new version differs by 13 commits .
c1a9ed0
fix(args): make args conversion stateless (#85)
920451d
docs(contributors): add @inyono (#83)
b59473a
docs(contributors): add @danielo515 (#81)
4799cc2
docs(README): Add compumike08 as a contributor (#79)
4fceddd
docs(badges): add appveyor badge
80b382e
chore(build): add appveyor (#76)
cdffc6e
docs: fix contributing nps references
a154170
docs: add wopian as contributor (#73)
967f472
fix(bin): babelify bin (#75)
dba0b39
docs: update path to release page (#71)
b303b9f
fix: bin require
85b8e8a
docs: contributor member (#66)
aae44df
fix: bin location
See the full diff.
devDependency
cross-env was updated from 5.2.0
to 5.2.1
.Your tests are still failing with this version. Compare changes
The new version differs by 56 commits.
a75fd0e
fix: remove is-windows dependency (#207)
4889923
docs: add note for windows issues
2b36bb3
docs: add Jason-Cooke as a contributor (#201)
41ab3b0
docs: Fix typo (#200)
553705c
docs(README): list @naholyr/cross-env in Other Solutions section (#189)
5d0f19f
docs: remove codesponsor (#186)
739fd62
feat(deps): upgrade cross-spawn (#182)
b88977c
fix: check for sigint before setting exit code to 1 (#181)
eb37984
docs: inform about signal events on Windows (#179)
d5170bf
fix: exit code should be set to 1 when os kills child process (#177)
450dae9
fix: allow backslash (#173)
5204dd6
docs: Fix typo (#166)
3c064d8
docs: Closes #153 with documentation update (#165)
3cf4170
fix: regex flag fix (#161)
7fa5c08
fix: handle escaping and single quotes (#158)
There are 56 commits in total.
See the full diff
Version 3.2.0 of cross-env just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As cross-env is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Status Details
- ❌ **wercker/build** Wercker pipeline failed [Details](https://app.wercker.com/GasBuddy/pg-ltree-util/runs/build/58bae34dd8145c01002648a4)Release Notes
v3.2.0<a name"3.2.0">
3.2.0 (2017-03-04)
Features
Commits
The new version differs by 4 commits .
dad00c4
feat(revamp): revamp the entire lib (backward compatible) (#63)
e33a85c
docs(README): Add doc for cross-var. (#58)
5e590ec
docs(README): added how to use cross-env to run npm sub-scripts (#53)
afdb2de
docs(README): mention Bash on Windows (#49)
See the full diff.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: