Skip to content

Update cucumber requirement from >= 4.0.0, < 9 to >= 4.0.0, < 13 in /allure-cucumber - #261

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/bundler/allure-cucumber/cucumber-gte-4.0.0-and-lt-13
Open

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/bundler/allure-cucumber/cucumber-gte-4.0.0-and-lt-13

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 15, 2026

Copy link
Copy Markdown
Contributor

Updates the requirements on cucumber to permit the latest version.

Release notes

Sourced from cucumber's releases.

v12.0.0

Added

  • Added new dependency on cucumber-query which is a new internal structure for all message based formatters to query the state of the test run (#1889 luke-hill & mattwynne)

Changed

  • Updated cucumber-compatibility-kit to v26
  • Refactor to internal error logic (No user facing changes)
  • Refactor to internal MessageBuilder logic (No user facing changes)
  • Cucumber::Runtime#ask which has not been actively supported is now deprecated (Should you wish to delay things and wait for input, either use a tool like pry or add a hard-coded sleep) (#1842 luke-hill)
  • Updated cucumber-expressions to v20
  • Updated cucumber-html-formatter to v24
  • Permit multi_test v2/v3 so we can begin to remove some legacy support
  • Updated cucumber-core to v20
  • All events now inherit from the new Cucumber::Core::Event::Base class (luke-hill)
  • Updated the MessageBuilder to not create the messages now created by cucumber-ruby-core (#1882 brasmusson)

Fixed

  • The testCaseFinished message now states willBeRetried correctly when --retry-total stops further retries, or when --retry is used at all (it was off by one), so the HTML formatter no longer drops or duplicates scenarios (#1905 Enceradeira)
  • Updated the html-formatter to access message stream correctly (#1899 brasmusson)

Removed

  • This was a long-standing feature that was used to determine if a test run should fail if there were any undefined, pending or flaky steps.
  • All non-passing scenarios (Except flaky with retry), are now considered failures
  • Removed the concept of strict from cucumber-ruby (luke-hill)
  • Removed a bunch of RSpec support logic that was no longer used in the codebase (This includes some legacy pending logic and some old rspec helper files)
  • Removed handling of a Ruby 2.1 system error (luke-hill)
  • Removed support for Ruby 3.1 and 3.2 (Minimum ruby is now 3.3) (luke-hill)
  • Removed the duplicated "new" base class for events - use Core::Event::Base instead (luke-hill)
Changelog

Sourced from cucumber's changelog.

[12.0.0] - 2026-10-12

Added

  • Added new dependency on cucumber-query which is a new internal structure for all message based formatters to query the state of the test run (#1889 luke-hill & mattwynne)

Changed

  • Updated cucumber-compatibility-kit to v26
  • Refactor to internal error logic (No user facing changes)
  • Refactor to internal MessageBuilder logic (No user facing changes)
  • Cucumber::Runtime#ask which has not been actively supported is now deprecated (Should you wish to delay things and wait for input, either use a tool like pry or add a hard-coded sleep) (#1842 luke-hill)
  • Updated cucumber-expressions to v20
  • Updated cucumber-html-formatter to v24
  • Permit multi_test v2/v3 so we can begin to remove some legacy support
  • Updated cucumber-core to v20
  • All events now inherit from the new Cucumber::Core::Event::Base class (luke-hill)
  • Updated the MessageBuilder to not create the messages now created by cucumber-ruby-core (#1882 brasmusson)

Fixed

  • The testCaseFinished message now states willBeRetried correctly when --retry-total stops further retries, or when --retry is used at all (it was off by one), so the HTML formatter no longer drops or duplicates scenarios (#1905 Enceradeira)
  • Updated the html-formatter to access message stream correctly (#1899 brasmusson)

Removed

  • This was a long-standing feature that was used to determine if a test run should fail if there were any undefined, pending or flaky steps.
  • All non-passing scenarios (Except flaky with retry), are now considered failures
  • Removed the concept of strict from cucumber-ruby (luke-hill)
  • Removed a bunch of RSpec support logic that was no longer used in the codebase (This includes some legacy pending logic and some old rspec helper files)
  • Removed handling of a Ruby 2.1 system error (luke-hill)
  • Removed support for Ruby 3.1 and 3.2 (Minimum ruby is now 3.3) (luke-hill)
  • Removed the duplicated "new" base class for events - use Core::Event::Base instead (luke-hill)

[11.1.1] - 2026-06-25

Changed

  • Change to use events to pass the data from "log" and "attach" calls from the step definitions to the formatters. With this the last part of the ancient (pre event) formatter inteface has been removed. (#1881 brasmusson)

Fixed

  • Fixed issue with html-formatter where attachments and envelopes were causing the entire message pool to be blank (#1891) luke-hill
  • Show failed step error details in the summary formatter output
  • Fixed up JRuby examples which weren't running due to anglicisation issues (Pivoted to use English step definitions to help JRuby testing)
  • Fixed up Arabic example which had some incorrect logic for step definition matching (Due to RTL nature of the language)

[11.1.0] - 2026-06-02

Added

  • Print thread backtraces on SIGINFO/SIGPWR (#1830) sobrinho
  • Added Suggestion messages that will show all the snippets for all message based formatters (#1870) luke-hill

Changed

... (truncated)

Commits
  • 495f50d Prepare release v12.0.0
  • 84f7ecf Add v12 upgrading notes (#1913)
  • 6ebca7a Styling tweaks
  • b7059a8 Update ruby/setup-ruby action to v1.328.0
  • 5cb6837 Report will_be_retried from the retry filter's decision (#1910)
  • ff5f86a Update github/codeql-action action to v4.38.3
  • 4344c1f Use GitHub's dedicated self-repository syntax (#1911)
  • 2ec5599 Update ruby/setup-ruby action to v1.327.0
  • 5cc5145 Update github/codeql-action action to v4.38.2
  • 729c98f Update ruby/setup-ruby action to v1.326.0
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Updates the requirements on [cucumber](https://github.com/cucumber/cucumber-ruby) to permit the latest version.
- [Release notes](https://github.com/cucumber/cucumber-ruby/releases)
- [Changelog](https://github.com/cucumber/cucumber-ruby/blob/main/CHANGELOG.md)
- [Commits](cucumber/cucumber-ruby@v4.0.0...v12.0.0)

---
updated-dependencies:
- dependency-name: cucumber
  dependency-version: 12.0.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Oct 15, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: type:dependency. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

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.

0 participants