An in-range update of pre-commit 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 1.2.1 of pre-commit just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | pre-commit |
| Current Version | 1.2.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As pre-commit is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
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 with the greenkeeper/pre-commit-1.2.1 branch and inspect the failed AppVeyor and CircleCI build details linked in the issue. Compare the dependency update from pre-commit 1.2.0 to 1.2.1, identify the build failure, and verify that the project checks pass after resolving it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100