Behavex

-------------------------------------------------------------------------------

ENHANCEMENTS:

* Support for Python 3.13
* Improvement done to replace the htmlmin library with minify-html, as htmlmin is deprecated.

-------------------------------------------------------------------------------

ENHANCEMENTS:

* Improvement done when reporting exceptions, as despite the traceback is being reported, the exception message was not being displayed.
* Improvement done to display the correct exit code when execution crashes in environment hooks.

-------------------------------------------------------------------------------

ENHANCEMENTS:

* Cosmetic improvements in documentation

FIXES:

* Fixing issue when re-executing failing scenarios using the -rf option, as there where scenario outline examples not being considered in the re-execution

-------------------------------------------------------------------------------

ENHANCEMENTS:

* Enable multiple BehaveX processes to run at the same time, by creating unique execution output files in temporary folders for each process.

FIXES:

* Avoid executing environment.py hooks when a dry run is performed.

-------------------------------------------------------------------------------

ENHANCEMENTS:

* Adding support for latest Python versions (3.12)
* Performing cross-platform validations as part of github actions workflow (Linux, Windows and MacOS)
* Enabling adding scenario lines in feature paths when running BehaveX
* Fixing issue when performing dry runs, as internal BHX_MANUAL_DRY_RUN tag was not removed from the scenario tags

FIXES:

* Fixing execution issues in Windows OS when running BehaveX with a feature path different than the current path.
* Fixing encoding issues in progress bar in Windows OS

-------------------------------------------------------------------------------
ENHANCEMENTS:

* Enhanced parallel scenario execution management by utilizing scenario lines over scenario names. This allows running scenarios that might change their name without causing issues in parallel executions.

FIXES:

* Avoid using the scenario name as part of the hash to generate output paths, as if the scenario name is changed, the path does not match. Instead, the feature filename and the line where the scenario is located is used to generate the hash.