An in-range update of unist-builder is breaking the build 🚨
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, node.js
- Domain
- build-system
Research direction
Start by opening the linked CircleCI failure details and comparing the unist-builder 1.0.2 to 1.0.3 update. Check the project's dependency configuration and run the existing build or tests to identify the failing step; done means the dependency update no longer breaks the build.
Written by the indexing model from the issue text.
Description
Version 1.0.3 of unist-builder was just published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | unist-builder |
| Current Version | 1.0.2 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
unist-builder is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
- ❌ ci/circleci: Your tests failed on CircleCI (Details).
Commits
The new version differs by 14 commits.
d0970961.0.326b611dAdd coverage testsb2959daRefactorreadme.mdd9e63b4Movetest/test.js>test.js450e41cRefactor code-style83b7f5aRefactorpackage.jsond8c8285MoveREADME.md>readme.md71978c1MoveLICENSE>license797874fAdd.npmrc10400f0Add.editorconfigbd6b1c5Update Node in Travis2c08694Update.gitignore3dd2863Refactor markdown93b2958Update Node in Travis
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from documentationjs/documentation-theme-utils
-
greenkeeper
Difficulty 4/5 3-5 days Newbie friendliness 25/100
documentationjs/documentation-theme-utils#17 · 2 comments ·
-
greenkeeper
Difficulty 3/5 1-2 days Newbie friendliness 25/100
documentationjs/documentation-theme-utils#16 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
greenkeeper
Difficulty 3/5 1-2 days Newbie friendliness 25/100
documentationjs/documentation-theme-utils#8 · 5 comments ·
-
Add a License fileOpen
Difficulty 1/5 Under an hour Newbie friendliness 25/100
All issues in documentationjs/documentation-theme-utils
Similar issues
-
[quality] useFocusTrap's Shift+Tab wrap and non-Tab/non-Escape key arms are never driven end to endPossibly taken @hivecommons-hive claimed this today. Openagent/quality hive/covered-by-pr hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/gh-aw-workshop#4220 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
JuliusBrussee/caveman#1189 ·
Maintainers usually reply within 1 day
-
priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenHands/extensions#738 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
invoiceninja/invoiceninja#13320 ·
Maintainers usually reply within 1 day