An in-range update of globals-docs is breaking the build 🚨
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- build-system, ci-cd
Research direction
Start with the Greenkeeper globals-docs-2.3.1 branch and the linked CircleCI job to identify the failing build step. Compare globals-docs 2.3.0 with 2.3.1 and verify the project build and tests pass with the dependency update; the issue is done when CI is green.
Written by the indexing model from the issue text.
Description
Version 2.3.1 of globals-docs was just published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | globals-docs |
| Current Version | 2.3.0 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
globals-docs 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 5 commits.
44ba37dchore(release): 2.3.15b037d8fix: Fix tests, remove unused dependencyb8a297dbuild: Use standard-version for releases95ce765fix: Remove /en-US/ from Mozilla docs (#4)d2815a2Update changelog
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 3/5 1-2 days Newbie friendliness 25/100
documentationjs/documentation-theme-utils#18 · 1 comment ·
-
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] coverage gate exits 0 when the test run is killed by a signal (tests/tools/coverage-report.mjs:680 `?? 1` is untested)Possibly 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 84/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
githubnext/gh-aw-workshop#4174 ·
Maintainers usually reply within 1 day
-
sendDefaultPii is reported as deprecated on ReactNativeOptions although dataCollection is hiddenOpenBug React-Native Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-react-native#6830 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
JuliusBrussee/caveman#1183 · 1 comment ·
Maintainers usually reply within 1 day