An in-range update of filesize is breaking the build 🚨
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Version 3.5.7 of filesize just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | filesize |
| Current Version | 3.5.6 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
filesize 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
- ✅ **coverage/coveralls** First build on greenkeeper/filesize-3.5.7 at 12.808% [Details](https://coveralls.io/builds/11303924),- ✅ **ci/circleci** Your tests passed on CircleCI! [Details](https://circleci.com/gh/leecade/fe/330?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link),- ✅ **continuous-integration/appveyor/branch** AppVeyor build succeeded [Details](https://ci.appveyor.com/project/leecade/fe/build/1.0.363),- ❌ **codecov/project** 12.31% (-0.5%) compared to fe5bfde [Details](https://codecov.io/gh/leecade/fe/commit/e10a0f70a8101d2da7e1f452e738fba25746b7f8),- ✅ **codecov/patch** Coverage not affected when comparing fe5bfde...e10a0f7 [Details](https://codecov.io/gh/leecade/fe/commit/e10a0f70a8101d2da7e1f452e738fba25746b7f8)Commits
The new version differs by 1 commits0.
2edf1a3Addingbabilitask to minify the es6 file, fixes #86
false
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 🌴
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 by comparing the filesize update from 3.5.6 to 3.5.7 and reviewing the failed greenkeeper/filesize-3.5.7 build reported in the issue. Run the repository's build and CI checks to reproduce the failure; done means the build passes with the dependency update or the project no longer breaks from it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100