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)