search

guilhermejcgois / generator-protractor-typescript

Generator for typescript projects that uses Protractor. Protractor is an end-to-end test framework for Angular and AngularJS applications. Protractor runs tests against your application running in a real browser, interacting with it as a user would.
MIT License
2 stars 0 forks source link

An in-range update of lint-staged is breaking the build 🚨 #46

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency lint-staged was updated from 9.0.2 to 9.1.0.

🚨 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.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/guilhermejcgois/generator-protractor-typescript/builds/554997242?utm_source=github_status&utm_medium=notification)).
Release Notes for v9.1.0

9.1.0 (2019-07-06)

Bug Fixes

  • snapshot with fully-resolved path name (b1a08b8)

Features

  • make node-api accessible (ca37906)
Commits

The new version differs by 9 commits.

  • 107402f test: improve test coverage
  • 76264eb test: improve test coverage
  • 0dee25b test: improve test coverage of printErrors
  • dd1100b docs: add node api to README
  • b1a08b8 fix: snapshot with fully-resolved path name
  • 06269dd refactor: return a Promise from the main entrypoint
  • 386ff4a refactor: convert main entrypoint to use an object
  • d8b3695 refactor: simplify bin declaration in package.json
  • ca37906 feat: make node-api accessible

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 5 years ago

After pinning to 9.0.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

Release Notes for v9.2.1

9.2.1 (2019-07-25)

Bug Fixes

  • pin commitizen@3.1.2 to support node 8 (ee774e3)
  • pin cz-conventional-changelog@2.1.0 to support node 8 (e879b6a)
  • remove empty spaces from warning (6126b72)
Commits

The new version differs by 16 commits.

  • e879b6a fix: pin cz-conventional-changelog@2.1.0 to support node 8
  • ee774e3 fix: pin commitizen@3.1.2 to support node 8
  • eb07cd5 chore: use jsonlint --in-place
  • 6126b72 fix: remove empty spaces from warning
  • 0ce85b2 chore: upgrade devDependencies and simplify eslint config
  • 34ab803 chore: upgrade production depedencies
  • 127cd95 refactor: set SIGINT listener in bin instead of runAll
  • 0342ebf test: update snapshots
  • 7a9df2f refactor: change 'linters' to 'tasks'
  • 7432469 test: add integration test for runAll
  • 8ba95d5 refactor: allow runAll and generateTasks to receive cwd
  • cf8a005 docs: add information about ignoring files
  • da0bbc7 docs: add --relative to README
  • 443ee90 test: add test for gitStashPop throwing
  • 242deb5 feat: add --relative option for controlling file paths

There are 16 commits in total.

See the full diff