Updates the requirements on cucumber to permit the latest version.

Sourced from cucumber's releases.

v11.0.0

Added

• Add timestamp to Attachment message
• Added a new option for running order --reverse which will run the scenarios in reverse order (#1807 luke-hill)
• A first initial iteration of the new cucumber-query structure (#1801 luke-hill)

This will be used for the migration of all existing formatters - becoming the building blocks for the future of cucumber formatters which will begin being migrated in the start of 2026

Changed

• Use the test result type 'ambiguous' added to cucumber-ruby-core when steps are ambiguous (#1815) brasmusson)
• Use the new internal cucumber-query structure for the rerun formatter

This is a very large refactor, but should not change any behaviour. The cucumber-query structure is a new internal structure that is designed to be used by formatters to query the state of the test run in a more intuitive way.

The rerun formatter was chosen as the first formatter to migrate to this new structure as it is one of the simpler formatters and will allow us to test the new structure in a real-world scenario.

• Updated cucumber-compatibility-kit to v22
• Security: Switched out IO.read for more secure File.read in a few areas of the codebase
• Implemented the new cucumber-query structure in all message based formatters (Currently HTML / Rerun and Message) (#1844 luke-hill)

Fixed

• Fix crash when Cucumber::Messages::Group#children is nil
• Fixed a longstanding issue that could affect formatters reporting of retried scenarios (Now each scenario should only be reported once, with the final result of the scenario) (#1844 luke-hill)
• Fixed an issue where the default flags derived in the Options and Configuration classes were not congruent (#1846) luke-hill)
• Fixed an issue where NoMethodError could be raised when declaring a parameter-type that used bound methods (#1789)

Sourced from cucumber's changelog.

[11.0.0] - 2026-04-14

Added

• Add timestamp to Attachment message
• Added a new option for running order --reverse which will run the scenarios in reverse order (#1807 luke-hill)
• A first initial iteration of the new cucumber-query structure (#1801 luke-hill)

This will be used for the migration of all existing formatters - becoming the building blocks for the future of cucumber formatters which will begin being migrated in the start of 2026

Changed

• Use the test result type 'ambiguous' added to cucumber-ruby-core when steps are ambiguous (#1815) brasmusson)
• Use the new internal cucumber-query structure for the rerun formatter

This is a very large refactor, but should not change any behaviour. The cucumber-query structure is a new internal structure that is designed to be used by formatters to query the state of the test run in a more intuitive way.

The rerun formatter was chosen as the first formatter to migrate to this new structure as it is one of the simpler formatters and will allow us to test the new structure in a real-world scenario.

• Updated cucumber-compatibility-kit to v22
• Security: Switched out IO.read for more secure File.read in a few areas of the codebase
• Implemented the new cucumber-query structure in all message based formatters (Currently HTML / Rerun and Message) (#1844 luke-hill)

Fixed

• Fix crash when Cucumber::Messages::Group#children is nil
• Fixed a longstanding issue that could affect formatters reporting of retried scenarios (Now each scenario should only be reported once, with the final result of the scenario) (#1844 luke-hill)
• Fixed an issue where the default flags derived in the Options and Configuration classes were not congruent (#1846) luke-hill)
• Fixed an issue where NoMethodError could be raised when declaring a parameter-type that used bound methods (#1789)

[10.2.0] - 2025-12-10

Changed

• Permit the latest version of the cucumber-html-formatter (v22.0.0+)
• Permit cucumber-expressions up to v19

[10.1.1] - 2025-10-08

Changed

• Internal refactors to CCK testing code to better check that the message formatter responses are as expected
• Simplify #attach by better checking the different use cases (base64 vs file path)

Fixed

• Prevent messages (And any consuming formatters), from not handling unknown (base64), media types (#1796 luke-hill)

[10.1.0] - 2025-08-20

Changed

• Updated cucumber-compatibility-kit to v20
• Optimised compatibility tests (That use the CCK), so that tests run slightly more optimal (Creating less empty arrays)

Fixed

... (truncated)

• cbf0352 Prepare release v11.0.0
• 296295b Update zizmorcore/zizmor-action action to v0.5.3
• 0f40013 Update ruby/setup-ruby action to v1.301.0
• 24f0615 fix: Fix NME raised when converting ParameterType to envelope (#1789)
• d265c2c Update dependency ruby to v3.4.9
• dfc6940 Bugfix/retried envelope message (#1844)
• a44d555 Refactor/spec tidy (#1850)
• 2283c1a Refactor/remove redundant constants (#1845)
• ea15ca0 Refactor/single source of truth for defaults (#1846)
• 82b8297 chore(deps): update ruby/setup-ruby action to v1.300.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.

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)