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 aegir is breaking the build 🚨 #18

Open
greenkeeper bot opened this issue Dec 18, 2017 · 2 comments
Open

An in-range update of aegir is breaking the build 🚨 #18

greenkeeper bot opened this issue Dec 18, 2017 · 2 comments

Comments

@greenkeeper
Copy link

greenkeeper bot commented Dec 18, 2017

Version 12.3.0 of aegir was just published.

Branch Build failing 🚨
Dependency aegir
Current Version 12.2.0
Type devDependency

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

aegir 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 is in progress Details
  • ci/circleci Your tests failed on CircleCI Details

Release Notes v12.3.0

Bug Fixes

  • release: correctly run tests on release (e7b544a), closes #172
  • process.env inacessible in browser tests (2ca2863)
  • update uglify config to not compress (and mess with js-ipfs) (17a28a6)
  • use rel paths on windows (#183) (d57dd3f)
  • test: inject missing webpack config into tests (bb4c0e4)

Features

  • test: output junit reports on CI (61ab915)
Commits

The new version differs by 17 commits.

  • dc56c03 chore: release version v12.3.0
  • 8a0476e chore: update contributors
  • f6d5302 Merge pull request #187 from ipfs/fix-env
  • c38dade chore(ci): slow things everywhere
  • 10683ca chore(scripts): set AEGIR_TEST for coverage
  • 751681b chore(ci): use cross-env to set env variables accross oses
  • bb4c0e4 fix(test): inject missing webpack config into tests
  • 41efd8d Revert "fix: process.env inacessible in browser tests"
  • 9fdd79f chore: fix release scripts
  • 61ab915 feat(test): output junit reports on CI
  • 7ff93b0 Merge pull request #179 from mkg20001/fix/process-env
  • d57dd3f fix: use rel paths on windows (#183)
  • 5b5f148 chore: update deps (#178)
  • 17a28a6 fix: update uglify config to not compress (and mess with js-ipfs)
  • 2ca2863 fix: process.env inacessible in browser tests

There are 17 commits in total.

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
Author

greenkeeper bot commented Dec 18, 2017

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

@greenkeeper
Copy link
Author

greenkeeper bot commented Jan 24, 2018

Version 12.4.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes v12.4.0

Features

  • run pre-push targets if there are any (858c1fd), closes #188
Commits

The new version differs by 5 commits.

  • d606a4f chore: release version v12.4.0
  • 4932152 chore: update contributors
  • 51b2672 Merge pull request #191 from ipfs/github-access-token
  • d67d10f docs: give advice on aegir release error
  • 858c1fd feat: run pre-push targets if there are any

See the full diff

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

0 participants