snasirca / mikado-graph-generator Goto Github PK

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    guard-bundler was resolved to 3.0.0, which depends on
      bundler (>= 2.1, < 3)

  Current Bundler version:
    bundler (1.17.3)
This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

Could not find gem 'bundler (>= 2.1, < 3)', which is required by gem 'guard-bundler', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    guard-bundler was resolved to 3.0.0, which depends on
      bundler (>= 2.1, < 3)

  Current Bundler version:
    bundler (1.17.3)
This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

Could not find gem 'bundler (>= 2.1, < 3)', which is required by gem 'guard-bundler', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

The failing build can probably be fixed just by updating the RuboCop offense, or moving the item to .rubocop_todo.yml. However, Travis is also suggesting moving to GitHub's native Dependabot, and the question of whether TravisCI or GitHub Actions are a better long-term option are worth discussing.

If the repository owner can add Dependabot to the project, I can provide a PR that fixes the RuboCop error that's causing Travis to fail. Meanwhile, I'd also like to know if refactoring to GitHub Actions instead of TravisCI for testing is worthwhile or desirable for the project. It's more work to refactor than to fix, but seems like it could be useful and fun to do.

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    guard-bundler was resolved to 3.0.0, which depends on
      bundler (>= 2.1, < 3)

  Current Bundler version:
    bundler (1.17.3)
This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

Could not find gem 'bundler (>= 2.1, < 3)', which is required by gem 'guard-bundler', in any of the sources.

Bundler could not find compatible versions for gem "rubocop":
  In snapshot (Gemfile.lock):
    rubocop (= 0.85.1)

  In Gemfile:
    rubocop (~> 0.52)

    guard-rubocop was resolved to 1.3.0, which depends on
      rubocop (~> 0.20)

    rubocop-rspec (>= 1.40.0, <= 1.42.0) was resolved to 1.42.0, which depends on
      rubocop (>= 0.87.0)

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

In a directed graph like Mikado, the graph should flow from the root node towards the leaves. So, the arrows should point to the dependencies rather than towards the goal, although the order of eventual refactorings will flow in the opposite direction. So, the directionality of dependencies should look more like the following:

Currently, the #depends_on method shows an inverted relationship, and the README provides no documented way to change the directionality.