An in-range update of baobab 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
Version 2.4.0 of baobab just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | baobab |
| Current Version | 2.3.4 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As baobab 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
- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
v2.4.0- Handling non-enumerable properties (@BrendanAnnable).
Commits
The new version differs by 6 commits .
3e6a08aChangelog aestheticse684187Bump 2.4.08d532f8Merge pull request #468 from BrendanAnnable/copy-descriptors5d873aeAdd testsd01d6b4Revert enumerable change for monkeysb995d26Add support for non-enumerable properties
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 opening the linked Travis CI build failure and comparing the greenkeeper/baobab-2.4.0 branch with the current project. Identify what baobab 2.4.0 breaks, then make the project build successfully with the dependency update and verify the result through the project’s CI checks.
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
- Mostly clear
- Newbie friendliness
- 35/100