search

AtomLinter / linter-glsl

Atom package that lints GLSL shaders on the fly.
https://atom.io/packages/linter-glsl
MIT License
15 stars 6 forks source link

An in-range update of atom-linter is breaking the build 🚨 #52

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 9.0.1 of atom-linter just got published.

Branch Build failing 🚨
Dependency atom-linter
Current Version 9.0.0
Type dependency

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

As atom-linter is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:

Status Details - ❌ **ci/circleci** Your tests failed on CircleCI [Details](https://circleci.com/gh/AtomLinter/linter-glsl/103?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Release Notes v9.0.1
  • Make exec and execNode behave the way they were supposed and documented to be by restoring their 10 seconds default timeout
Commits

The new version differs by 5 commits .

  • b6628dd :arrow_up: Bump version to 9.0.1
  • c742fc3 :no_entry: Ignore decls in npm
  • f40065e Merge pull request #155 from steelbrain/steelbrain/restore-default-timeout
  • 2206607 :arrow_up: Upgrade specs to match latest behavior
  • 8096e6b :bug: Restore 10 seconds timeout

See the full diff.

Not sure how things should work exactly? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

Arcanemagus commented 7 years ago

CI failures dealt with in #54. They were unrelated to the update of atom-linter@9.0.1.