-
Notifications
You must be signed in to change notification settings - Fork 0
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
Upgrade cucumber to version 6.1.0 #7
base: +master+master+master+
Are you sure you want to change the base?
Conversation
github_api.gemspec : should be # frozen_string_literal: true
require_relative "lib/github_api/version"
Gem::Specification.new do |gem|
gem.name = "github_api"
gem.version = Github::VERSION
gem.authors = ["Piotr Murach"]
gem.email = ["[email protected]"]
gem.homepage = "http://piotrmurach.github.io/github/"
gem.summary = "Ruby client for the official GitHub API"
gem.description = %q{ Ruby client that supports all of the GitHub API methods. It"s build in a modular way, that is, you can either instantiate the whole api wrapper Github.new or use parts of it e.i. Github::Client::Repos.new if working solely with repositories is your main concern. Intuitive query methods allow you easily call API endpoints. }
gem.license = "MIT"
gem.required_ruby_version = ">= 2.0.0"
- gem.files = Dir["lib/**/*"]
+ gem.diff = Dir["lib/**/*"]
gem.require_paths = %w[ lib ]
- gem.extra_rdoc_files = ["LICENSE.txt", "README.md", "CHANGELOG.md"]
+ gem.extra_rdoc_diff = ["LICENSE.txt", "README.md", "CHANGELOG.md"]
gem.add_dependency "addressable", "~> 2.4"
gem.add_dependency "hashie", "~> 3.5", ">= 3.5.2"
gem.add_dependency "faraday", ">= 0.8", "< 2"
gem.add_dependency "oauth2", "~> 1.0"
gem.add_dependency "descendants_tracker", "~> 0.0.4"
gem.add_development_dependency "bundler", ">= 1.5.0"
gem.add_development_dependency "rake"
gem.add_development_dependency "cucumber", "~> 6.1"
gem.add_development_dependency "rspec", "~> 3"
gem.add_development_dependency "rspec-its","~> 1"
gem.add_development_dependency "vcr", "~> 3.0.3"
gem.add_development_dependency "webmock", "~> 3.8"
end |
Hey! Changelogs info seems to be missing or might be in incorrect format. |
ContributorsCommit-Lint commandsYou can trigger Commit-Lint actions by commenting on this PR:
|
github_api.gemspec : should be # frozen_string_literal: true
require_relative "lib/github_api/version"
Gem::Specification.new do |gem|
gem.name = "github_api"
gem.version = Github::VERSION
gem.authors = ["Piotr Murach"]
gem.email = ["[email protected]"]
gem.homepage = "http://piotrmurach.github.io/github/"
gem.summary = "Ruby client for the official GitHub API"
gem.description = %q{ Ruby client that supports all of the GitHub API methods. It"s build in a modular way, that is, you can either instantiate the whole api wrapper Github.new or use parts of it e.i. Github::Client::Repos.new if working solely with repositories is your main concern. Intuitive query methods allow you easily call API endpoints. }
gem.license = "MIT"
gem.required_ruby_version = ">= 2.0.0"
- gem.files = Dir["lib/**/*"]
+ gem.title, = Dir["lib/**/*"]
gem.require_paths = %w[ lib ]
- gem.extra_rdoc_files = ["LICENSE.txt", "README.md", "CHANGELOG.md"]
+ gem.extra_rdoc_title, = ["LICENSE.txt", "README.md", "CHANGELOG.md"]
gem.add_dependency "addressable", "~> 2.4"
gem.add_dependency "hashie", "~> 3.5", ">= 3.5.2"
gem.add_dependency "faraday", ">= 0.8", "< 2"
gem.add_dependency "oauth2", "~> 1.0"
gem.add_dependency "descendants_tracker", "~> 0.0.4"
gem.add_development_dependency "bundler", ">= 1.5.0"
gem.add_development_dependency "rake"
gem.add_development_dependency "cucumber", "~> 6.1"
gem.add_development_dependency "rspec", "~> 3"
gem.add_development_dependency "rspec-its","~> 1"
gem.add_development_dependency "vcr", "~> 3.0.3"
gem.add_development_dependency "webmock", "~> 3.8"
end |
Unable to locate .performanceTestingBot config file |
This pull request seems genuine |
Pull request analysis by VIZIPI Below you will find who is the most qualified team member to review your code. No other active qualified developers found to review these specific changes. You might consider involving more team members with these code segments. Potential missing files from this Pull requestNo files found with a 40% threashold :) Committed file ranks(click to expand)0.00% [github_api.gemspec] |
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ cucumber (~> 2.1 → ~> 6.1) · Repo · Changelog
Release Notes
6.1.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 19 commits:
Release v6.1.0
Fix dry run with messages (#1540)
Remove deep clone of step arguments (#1538)
Revert "Add support for message formatters with dry runs (#1537)" (#1539)
Add support for message formatters with dry runs (#1537)
Fix 'attach' when passing null byte in the data (#1536)
Replace with in some places
Report empty scenarios with the json formatter (#1533)
Tell older bundlers which default branch to use
Modernise calls to bundler
Whitespace
Try adding a cache version so I can reset it
Rename master to main
Merge pull request #1528 from cucumber/undeprecate-json-formatter
Update CLI help message
Remove deprecation for the JSON formatter
Merge pull request #1527 from jmoglesby/patch-1
Switch first line back to original
Clarify removal of `puts` in CHANGELOG
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands