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

Update dependency rubocop-rspec to v2.31.0 #82

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 4, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
rubocop-rspec (changelog) '2.25.0' -> '2.31.0' age adoption passing confidence

Release Notes

rubocop/rubocop-rspec (rubocop-rspec)

v2.31.0: RuboCop RSpec v2.31.0

Compare Source

  • Support AutoCorrect: contextual option for LSP. (@​ydah)

v2.30.0: RuboCop RSpec v2.30.0

Compare Source

v2.29.2

Compare Source

  • Fix beginless and endless range bug for RepeatedIncludeExample cop. ([@​hasghari])
  • Fix a false positive for RSpec/RepeatedSubjectCall when subject is used as argument to function call. ([@​K-S-A])

v2.29.1

Compare Source

  • Fix an error in the default configuration. ([@​ydah])

v2.29.0

Compare Source

  • Fix an autocorrect error for RSpec/ExpectActual. ([@​bquorning])
  • Add new RSpec/UndescriptiveLiteralsDescription cop. ([@​ydah])
  • Add new RSpec/EmptyOutput cop. ([@​bquorning])

v2.28.0

Compare Source

  • Extract RSpec Rails cops to a separate repository, rubocop-rspec_rails. The rubocop-rspec_rails repository is a dependency of rubocop-rspec and the cops related to rspec-rails are aliased (RSpec/Rails/Foo == RSpecRails/Foo) until v3.0 is released, so the change will be invisible to users until then. ([@​ydah])

v2.27.1

Compare Source

  • Fix a false positive for RSpec/RepeatedSubjectCall when subject.method_call. ([@​ydah])
  • Add configuration option OnlyStaticConstants to RSpec/DescribedClass. ([@​ydah])

v2.27.0

Compare Source

  • Add new RSpec/IsExpectedSpecify cop. ([@​ydah])
  • Add new RSpec/RepeatedSubjectCall cop. ([@​drcapulet])
  • Add support for assert_true, assert_false, assert_not_equal, assert_not_nil, *_empty, *_predicate, *_kind_of, *_in_delta, *_match, *_instance_of and *_includes assertions in RSpec/Rails/MinitestAssertions. ([@​ydah], [@​G-Rath])
  • Support asserts with messages in Rspec/BeEmpty. ([@​G-Rath])
  • Fix a false positive for RSpec/ExpectActual when used with rspec-rails routing matchers. ([@​naveg])
  • Add configuration option ResponseMethods to RSpec/Rails/HaveHttpStatus. ([@​ydah])
  • Fix a false negative for RSpec/DescribedClass when class with constant. ([@​ydah])
  • Fix a false positive for RSpec/ExampleWithoutDescription when specify with multi-line block and missing description. ([@​ydah])
  • Fix an incorrect autocorrect for RSpec/ChangeByZero when compound expectations with line break before .by(0). ([@​ydah])

v2.26.1

Compare Source

  • Fix an error for RSpec/SharedExamples when using examples without argument. ([@​ydah])

v2.26.0

Compare Source

  • Add new RSpec/RedundantPredicateMatcher cop. ([@​ydah])
  • Add new RSpec/RemoveConst cop. ([@​swelther])
  • Add support for correcting "it will" (future tense) for RSpec/ExampleWording. ([@​jdufresne])
  • Add support for symbol style for RSpec/SharedExamples. ([@​jessieay])
  • Ensure PendingWithoutReason can detect violations inside shared groups. ([@​robinaugh])

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@yegor256
Copy link
Owner

yegor256 commented Jan 4, 2024

@rultor please, try to merge, since 7 checks have passed

@rultor
Copy link
Collaborator

rultor commented Jan 4, 2024

@rultor please, try to merge, since 7 checks have passed

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor
Copy link
Collaborator

rultor commented Jan 4, 2024

@rultor please, try to merge, since 7 checks have passed

@renovate[bot] @yegor256 Oops, I failed. You can see the full log here (spent 6min)

    \u001b[32mGiven I have a "\u001b[32m\u001b[1m.cobench\u001b[0m\u001b[0m\u001b[32m" file with content:\u001b[90m # features/step_definitions/steps.rb:41\u001b[0m\u001b[0m
\u001b[32m      """\u001b[0m
\u001b[32m      --verbose\u001b[0m
\u001b[32m\u001b[0m
\u001b[32m      --coder=john\u001b[0m
\u001b[32m      """\u001b[0m
To use retry middleware with Faraday v2.0+, install `faraday-retry` gem
    \u001b[32mWhen I run bin/cobench with "\u001b[32m\u001b[1m--dry\u001b[0m\u001b[0m\u001b[32m"\u001b[90m          # features/step_definitions/steps.rb:46\u001b[0m\u001b[0m
    \u001b[32mThen Stdout contains "\u001b[32m\u001b[1mXML saved to\u001b[0m\u001b[0m\u001b[32m"\u001b[90m          # features/step_definitions/steps.rb:52\u001b[0m\u001b[0m
    \u001b[32mAnd Exit code is zero\u001b[90m                        # features/step_definitions/steps.rb:60\u001b[0m\u001b[0m

Feature: Gem Package
  As a source code writer I want to be able to
  package the Gem into .gem file

  Scenario: Gem can be packaged                  \u001b[90m# features/gem_package.feature:5\u001b[0m
    \u001b[32mGiven I have a "\u001b[32m\u001b[1mexecs.rb\u001b[0m\u001b[0m\u001b[32m" file with content:\u001b[90m # features/step_definitions/steps.rb:41\u001b[0m\u001b[0m
\u001b[32m      """\u001b[0m
\u001b[32m      #!/usr/bin/env ruby\u001b[0m
\u001b[32m      require 'rubygems'\u001b[0m
\u001b[32m      spec = Gem::Specification::load('./spec.rb')\u001b[0m
\u001b[32m      if spec.executables.empty?\u001b[0m
\u001b[32m        fail 'no executables: ' + File.read('./spec.rb')\u001b[0m
\u001b[32m      end\u001b[0m
\u001b[32m      """\u001b[0m
/tmp/test20240104-938-19lvxz6/cobench/lib/cobench/version.rb:26: warning: already initialized constant Cobench::VERSION
/home/r/repo/lib/cobench/version.rb:26: warning: previous definition of VERSION was here
    \u001b[32mWhen I run bash with:\u001b[90m                        # features/step_definitions/steps.rb:74\u001b[0m\u001b[0m
\u001b[32m      """\u001b[0m
\u001b[32m      cd cobench\u001b[0m
\u001b[32m      gem build cobench.gemspec\u001b[0m
\u001b[32m      gem specification --ruby cobench-*.gem > ../spec.rb\u001b[0m
\u001b[32m      cd ..\u001b[0m
\u001b[32m      ruby execs.rb\u001b[0m
\u001b[32m      """\u001b[0m
    \u001b[32mThen Exit code is zero\u001b[90m                       # features/step_definitions/steps.rb:60\u001b[0m\u001b[0m

\u001b[31mFailing Scenarios:\u001b[0m
\u001b[31mcucumber features/cli.feature:18\u001b[0m\u001b[90m # Scenario: Simple report through real GitHub API\u001b[0m

6 scenarios (\u001b[31m1 failed\u001b[0m, \u001b[32m5 passed\u001b[0m)
18 steps (\u001b[31m1 failed\u001b[0m, \u001b[36m1 skipped\u001b[0m, \u001b[32m16 passed\u001b[0m)
4m1.126s
\u001b[1m\u001b[32m┌──────────────────────────────────────────────────────────────────────────────┐\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m Share your Cucumber Report with your team at \u001b[4m\u001b[1m\u001b[36mhttps://reports.cucumber.io\u001b[0m\u001b[0m\u001b[0m     \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m                                                                              \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m Command line option:    \u001b[36m--publish\u001b[0m                                            \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m Environment variable:   \u001b[36mCUCUMBER_PUBLISH_ENABLED\u001b[0m=\u001b[36mtrue\u001b[0m                        \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m cucumber.yml:           \u001b[36mdefault: --publish\u001b[0m                                   \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m                                                                              \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m More information at \u001b[4m\u001b[1m\u001b[36mhttps://cucumber.io/docs/cucumber/environment-variables/\u001b[0m\u001b[0m\u001b[0m \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m                                                                              \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m To disable this message, specify \u001b[1mCUCUMBER_PUBLISH_QUIET=true\u001b[0m or use the      \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m \u001b[1m--publish-quiet\u001b[0m option. You can also add this to your \u001b[1mcucumber.yml:\u001b[0m          \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m│\u001b[0m\u001b[0m \u001b[1mdefault: --publish-quiet\u001b[0m                                                     \u001b[1m\u001b[32m│\u001b[0m\u001b[0m
\u001b[1m\u001b[32m└──────────────────────────────────────────────────────────────────────────────┘\u001b[0m\u001b[0m
Coverage report generated for Cucumber Features, Unit Tests to /home/r/repo/coverage. 0 / 0 LOC (100.0%) covered.
Stopped processing SimpleCov as a previous error not related to SimpleCov has been detected
container 58432a863a49c6dcc5d36c9f0cf8f0dfbcd7517f5c1e8ac7c3ef8ee907868c11 is dead
Thu Jan  4 05:34:57 PM CET 2024

@renovate renovate bot changed the title Update dependency rubocop-rspec to v2.26.0 Update dependency rubocop-rspec to v2.26.1 Jan 5, 2024
@renovate renovate bot force-pushed the renovate/rubocop-rspec-2.x branch from e2b0022 to c38321d Compare January 5, 2024 17:07
@renovate renovate bot changed the title Update dependency rubocop-rspec to v2.26.1 Update dependency rubocop-rspec to v2.27.0 Mar 1, 2024
@renovate renovate bot force-pushed the renovate/rubocop-rspec-2.x branch from c38321d to 4a259f7 Compare March 1, 2024 01:52
@renovate renovate bot changed the title Update dependency rubocop-rspec to v2.27.0 Update dependency rubocop-rspec to v2.27.1 Mar 4, 2024
@renovate renovate bot force-pushed the renovate/rubocop-rspec-2.x branch from 4a259f7 to b1e602a Compare March 4, 2024 00:14
@renovate renovate bot changed the title Update dependency rubocop-rspec to v2.27.1 Update dependency rubocop-rspec to v2.28.0 Mar 29, 2024
@renovate renovate bot force-pushed the renovate/rubocop-rspec-2.x branch 2 times, most recently from aa44ebb to 0a4d351 Compare April 4, 2024 22:33
@renovate renovate bot changed the title Update dependency rubocop-rspec to v2.28.0 Update dependency rubocop-rspec to v2.29.0 Apr 4, 2024
@renovate renovate bot changed the title Update dependency rubocop-rspec to v2.29.0 Update dependency rubocop-rspec to v2.29.1 Apr 5, 2024
@renovate renovate bot force-pushed the renovate/rubocop-rspec-2.x branch from 0a4d351 to 5431bb9 Compare April 5, 2024 01:36
@renovate renovate bot force-pushed the renovate/rubocop-rspec-2.x branch from 5431bb9 to b7038b9 Compare May 3, 2024 01:36
@renovate renovate bot changed the title Update dependency rubocop-rspec to v2.29.1 Update dependency rubocop-rspec to v2.29.2 May 3, 2024
@renovate renovate bot changed the title Update dependency rubocop-rspec to v2.29.2 Update dependency rubocop-rspec to v2.30.0 Jun 3, 2024
@renovate renovate bot force-pushed the renovate/rubocop-rspec-2.x branch from b7038b9 to c67d0b3 Compare June 3, 2024 12:52
@renovate renovate bot force-pushed the renovate/rubocop-rspec-2.x branch from c67d0b3 to 412e6bf Compare June 7, 2024 09:43
@renovate renovate bot changed the title Update dependency rubocop-rspec to v2.30.0 Update dependency rubocop-rspec to v2.31.0 Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants