An in-range update of tap is breaking the build 🚨

Open
#8 5 comments 0 reactions 0 assignees View on GitHub

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
Domain
ci-cd, testing-qa

Research direction

Start by checking the tap devDependency declaration and the failed ci/circleci run linked in the issue. Compare tap 10.5.2 with 10.6.0 and identify the build failure; done means the dependency update is compatible and the CircleCI tests pass.

Written by the indexing model from the issue text.

Description

greenkeeper

Version 10.6.0 of tap just got published.

Branch Build failing 🚨
Dependency tap
Current Version 10.5.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As tap 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
  • ❌ ci/circleci Your tests failed on CircleCI Details
Commits

The new version differs by 7 commits.

  • 090a8ee v10.6.0
  • f60b003 fix rcfile test for grep and grepInvert fields
  • 0e36c2a doc TAP_GREP and TAP_GREP_INVERT environs in cli usage
  • 780f14a inherit grepInvert as well as greps
  • b4a6c8f update tests for grepInvert fix
  • 3c62917 grepInvert defaults to false, not []
  • 7e94cfc add --grep option

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 🌴

Dominant language
JavaScript
Stars
1
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from documentationjs/documentation-theme-utils

All issues in documentationjs/documentation-theme-utils

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.