Files
2026-08-30 22:02:02 +00:00

892 B

Description

Please include a summary of the change and include relevant motivation and context.

...

Checklist:

  • The make buildall command has been run successfully without any error or warning.
  • Any new code line is covered by unit tests and the coverage has not dropped.
  • Any new code follows the style guidelines of this project.
  • The code changes have been self-reviewed.
  • Corresponding changes to the documentation have been made.

The maintainer bumps the VERSION file at release time. Do not change it in your PR.

Type of change:

  • Minor non-breaking change (e.g., bug fix, dependencies updates).
  • New feature (non-breaking change which adds functionality).
  • Breaking change (fix or feature that would cause existing functionality to not work as expected).
  • Automation.
  • Documentation.
  • Example.
  • Testing.