Update cucumber requirement from >= 4.0.0, < 9 to >= 4.0.0, < 11 in /allure-cucumber

[dependabot]

Updates the requirements on cucumber to permit the latest version.

Release notes

Sourced from cucumber's releases.

v10.0.0

Changed

• Added dependencies that will no longer be part of the ruby stdlib (jeromeag)
• NB: This change has also facilitated a tweak to some output messages to include new fields such as testRunStartedId for full changes and expectations of what will be new check the messages (luke-hill)
• Updated cucumber-compatibility-kit to v18
• Changed compatibility testing to fully lean on external assets instead of duplicating them (luke-hill)
• Permit usage of latest versions of all cucumber internal gems
• The auto-generation of all placeholder pending steps has been refactored (There should be no visible changes but the code is now refactored to work using newer ruby standards)
• The #text? method for checking Differences in multi-line text is now deprecated (Users should lean on an appropriate testing library for this)
• Cucumber.use_legacy_autoloader that was intended as a stop-gap for v4/v5 is now deprecated (People that need to rely on procedural loading / reloading of files should use method invocations) (luke-hill)
• The backtrace filtering logic has been changed (There should be no visible changes but the code is now refactored to use newer, less procedural ruby)

Fixed

• Fixed an issue where a change to one example in compatibility testing wasn't fully adhered to (luke-hill)
• Fixed Ruby 3.4+ issue where error backtraces weren't being formatted. (#1771 orien)
• Fix some problematic specs that were leaking state and showcasing an issue on JRuby (#1783 luke-hill)

Removed

• StepDefinitionLight associated methods. The class itself is present but deprecated
• Webrick Proc handling aliases that were long redundant
• Associated legacy scripts for updating dependencies that are no longer used
• Tag Expressions using legacy syntax that were handled / sanitized are no longer done so (This applies to both regular usage and internal testing)
• Removed support for Ruby 2.7 and 3.0 (Minimum ruby is now 3.1) (luke-hill)
• Unindentation support for snippet generator / tests (Heredocs are much better now) (luke-hill)

Changelog

Sourced from cucumber's changelog.

[10.0.0] - 2025-06-11

Changed

• Added dependencies that will no longer be part of the ruby stdlib (jeromeag)
• NB: This change has also facilitated a tweak to some output messages to include new fields such as testRunStartedId for full changes and expectations of what will be new check the messages (luke-hill)
• Updated cucumber-compatibility-kit to v18
• Changed compatibility testing to fully lean on external assets instead of duplicating them (luke-hill)
• Permit usage of latest versions of all cucumber internal gems
• The auto-generation of all placeholder pending steps has been refactored (There should be no visible changes but the code is now refactored to work using newer ruby standards)
• The #text? method for checking Differences in multi-line text is now deprecated (Users should lean on an appropriate testing library for this)
• Cucumber.use_legacy_autoloader that was intended as a stop-gap for v4/v5 is now deprecated (People that need to rely on procedural loading / reloading of files should use method invocations) (luke-hill)
• The backtrace filtering logic has been changed (There should be no visible changes but the code is now refactored to use newer, less procedural ruby)

Fixed

• Fixed an issue where a change to one example in compatibility testing wasn't fully adhered to (luke-hill)
• Fixed Ruby 3.4+ issue where error backtraces weren't being formatted. (#1771 orien)
• Fix some problematic specs that were leaking state and showcasing an issue on JRuby (#1783 luke-hill)

Removed

• StepDefinitionLight associated methods. The class itself is present but deprecated
• Webrick Proc handling aliases that were long redundant
• Associated legacy scripts for updating dependencies that are no longer used
• Tag Expressions using legacy syntax that were handled / sanitized are no longer done so (This applies to both regular usage and internal testing)
• Removed support for Ruby 2.7 and 3.0 (Minimum ruby is now 3.1) (luke-hill)
• Unindentation support for snippet generator / tests (Heredocs are much better now) (luke-hill)

[9.2.1] - 2025-01-12

Fixed

• Fixed an issue for Ruby 3.4+ where a default hash instantiation was being picked up as keyword arguments (Jon Rowe)

[9.2.0] - 2024-03-19

Changed

• Updated cucumber dependencies (Specifically cucumber-core) (luke-hill)
• Uncoupled a lot of dual-responsibility complexity in HTTP classes (Specifically the builders/parsers) (#1752 luke-hill)

Removed

• Some legacy JRuby local testing profiles are now removed (luke-hill)

[9.1.2] - 2024-01-23

Changed

• Moved all CCK step definition/miscellaneous file logic from CCK gem to this repo. All logic contained in compatibility (luke-hill)
• Cleared up a few Layout/Linting cop offenses (#1750 luke-hill)

... (truncated)

Commits

• 2cf3a61 Prepare release v10.0.0
• 95f50c9 V10: Update dependencies (#1782)
• c93bde2 bugfix: Fix up problematic interceptor specs (JRuby issues on global state le...
• a21aea7 fix: Version number in VERSION file (#1784)
• 1f17266 Fix error backtrace formatting on Ruby 3.4+ (#1771)
• 328fd2b Update 10.0.0.md
• d10d094 Reintroduce cleaned up 9.2.1 into main (#1776)
• 89b8990 V10: Initial rework (#1759)
• 5cec922 Use correct Cucumber branding
• 9be96f3 Add Cucumber logo
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[dependabot]

Reviewers

The following users could not be added as reviewers: andrcuns. Either the username does not exist or it does not have the correct permissions to be added as a reviewer.

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.

[dependabot]

The reviewers field in the dependabot.yml file will be removed soon. Please use the code owners file to specify reviewers for Dependabot PRs. For more information, see this blog post.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.