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

[CVE-2017-8418] - updating rubocop dependency. #6

Merged
merged 2 commits into from
Dec 21, 2017

Conversation

majormoses
Copy link
Member

@majormoses majormoses commented Nov 20, 2017

Misc changes:

  • changelog location updates

Signed-off-by: Ben Abrams [email protected]

Pull Request Checklist

sensu-plugins/community#77

General

  • Update Changelog following the conventions laid out on Keep A Changelog

  • Update README with any necessary configuration snippets

  • Binstubs are created if needed

  • RuboCop passes

  • Existing tests pass

Purpose

Resolve CVE (see parent issue for details)

Known Compatibility Issues

Requires ruby 2.1 or greater

Misc changes:
- changelog location updates

Signed-off-by: Ben Abrams <[email protected]>
@majormoses majormoses self-assigned this Nov 20, 2017
@majormoses majormoses requested a review from eheydrick November 20, 2017 18:25
```
Bundler could not find compatible versions for gem "ruby":
  In Gemfile:
    ruby
    bundler (~> 1.7) was resolved to 1.16.0, which depends on
      ruby (>= 1.8.7)
    pry (~> 0.10) was resolved to 0.11.3, which depends on
      ruby (>= 1.9.3)
    rubocop (~> 0.51.0) was resolved to 0.51.0, which depends on
      ruby (>= 2.1.0)
    sensu-plugins-ansible was resolved to 1.0.0, which depends on
      ruby (>= 2.0.0)
```

Signed-off-by: Ben Abrams <[email protected]>
@majormoses majormoses merged commit 4ed4a55 into master Dec 21, 2017
@majormoses
Copy link
Member Author

@jaredledvina jaredledvina deleted the fix/CVE-2017-8418 branch May 20, 2019 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants