The devDependency husky was updated from 3.0.2 to 3.0.3.

🚨 View failing branch.

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

husky is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency lint-staged was updated from 9.2.3 to 9.2.4.

🚨 View failing branch.

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

lint-staged is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @types/node was updated from 12.7.0 to 12.7.1.

🚨 View failing branch.

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

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency ts-jest was updated from 24.0.2 to 24.1.0.

🚨 View failing branch.

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

ts-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @types/lodash was updated from 4.14.137 to 4.14.138.

🚨 View failing branch.

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

@types/lodash is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency semantic-release was updated from 15.13.26 to 15.13.27.

🚨 View failing branch.

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

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hello , the following config options do not seem to work as expected.

Issue Summary:

• Files are not displayed when using these two options for "created" and "createdOrModified"
• Code coverage report is correctly displayed when using "all"

Investigation Results:

• possibly filterForCoveredFiles is failing to return an array of files
• seems like file paths are not in sync for files found with danger.git.modified_files vs files from coverage

My setup:

• using "danger-plugin-istanbul-coverage": "^1.6.2",

• Followed the documentation for this setup https://danger.systems/js/plugins/danger-plugin-istanbul-coverage.html

const coverageConfig = {
  coveragePath: {
    path: path.resolve(
      __dirname,
      "...customPath/coverage-summary.json"
    ),
    type: "json-summary"
  },
  reportMode: "warn",
  entrySortMethod: "least-coverage",
  reportFileSet: "createdOrModified",
  numberOfEntries: 20,
  threshold: {
    statements: 40,
    branches: 40,
    functions: 40,
    lines: 40
  }
};

The devDependency @types/jest was updated from 24.0.18 to 24.0.19.

🚨 View failing branch.

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

@types/jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

name: Danger JS
on:
pull_request:
branches: [ develop ]
push:
branches: [ develop, main ]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Use node version from .nvmrc
uses: actions/setup-node@v1
with:
node-version: "${{ steps.nvm.outputs.NVMRC }}"
- name: Danger
run: npx danger ci
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Looks like gitHub actions is looking for node modules when running dangerfile. Is there a way I can run istanbul coverage on github.

Hi.

I have my coverage from jest, both in json and json-summary formats.
Either of them results in Coverage data had invalid formatting at path error.

Do you have any tips?

dangerfile:

import {danger, schedule, warn} from 'danger';
import {istanbulCoverage} from 'danger-plugin-istanbul-coverage';

schedule(
  istanbulCoverage({
    // Add a maximum number of entries to display
    numberOfEntries: 10,

    // // The location of the istanbul coverage file.
    coveragePath: '.coverageJest/coverage-summary.json',
  }),
);

Can we add coverage diff for files between pull request and master? It would be very helpful, we will able see coverage increase or decrease and even restrict coverage decreasing for project. I can help implement this one, but firstly wanted to hear you thoughts on it

issue is occurring when using the createdOrModifed config option

If the created or modified list contains only files with 0 code coverage then the wrong message appears

See examples below (2 PRS)