Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of rollup-plugin-typescript2 is breaking the build 🚨 #359

Closed
greenkeeper bot opened this issue Dec 3, 2019 · 2 comments
Closed

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Dec 3, 2019

The dependency rollup-plugin-typescript2 was updated from 0.25.2 to 0.25.3.

🚨 View failing branch.

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

rollup-plugin-typescript2 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
  • Test on node 12.x and macOS-latest: null
  • Test on node 12.x and windows-latest: null
  • Test on node 12.x and ubuntu-latest: null
  • Test on node 10.x and macOS-latest: null
  • Test on node 10.x and windows-latest: null
  • Test on node 10.x and ubuntu-latest: null
  • Test on node 8.12.x and macOS-latest: null
  • Test on node 8.12.x and windows-latest: null
  • Test on node 8.12.x and ubuntu-latest: null

Release Notes for 0.25.3

cwd option

Commits

The new version differs by 4 commits.

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 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 3, 2019

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

@agilgur5
Copy link
Collaborator

agilgur5 commented Mar 9, 2020

Was probably failing because of the persistent CI issues that #504 fixed. This was superseded by #506

@agilgur5 agilgur5 closed this as completed Mar 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant