maple3142 / maple3142/mapleutil
An in-range update of cross-env is breaking the build 🚨
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
## The devDependency [cross-env](https://github.com/kentcdodds/cross-env) was updated from `5.2.0` to `5.2.1`.
🚨 [View failing branch](https://github.com/maple3142/mapleutil/compare/master...maple3142:greenkeeper%2Fcross-env-5.2.1).
This version is **covered** by your **current version range** and after updating it in your project **the build failed**.
cross-env is a devDependency of this project. It **might not break your production code or affect downstream projects**, but probably breaks your build or test tools, which may **prevent deploying or publishing**.
Status Details
- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/maple3142/mapleutil/builds/579235941?utm_source=github_status&utm_medium=notification)).
---
Release Notes for v5.2.1
5.2.1 (2019-08-31)
Bug Fixes
Commits
The new version differs by 6 commits.
a75fd0efix: remove is-windows dependency (#207)4889923docs: add note for windows issues2b36bb3docs: add Jason-Cooke as a contributor (#201)41ab3b0docs: Fix typo (#200)553705cdocs(README): list @naholyr/cross-env in Other Solutions section (#189)5d0f19fdocs: remove codesponsor (#186)
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
---
Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the failing branch comparison and the linked Travis CI build to identify why cross-env 5.2.1 breaks the project. Compare the dependency changes from 5.2.0 to 5.2.1, then verify that the build passes after the required fix or dependency decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100