Please check if the PR fulfills these requirements
[ ] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
Does this PR already have an issue describing the problem?
What kind of change does this PR introduce?
Bug fix: version was incorrect in file for new crac version.
What is the current behavior?
The retro compatibility test for v2.3 was called instead of the one for v2.4, no visible behavior change until someone need to add changes verifications v2.4 version.
What is the new behavior (if this is a feature change)?
The retro compatibility test for v2.4 is called.
Does this PR introduce a breaking change or deprecate an API?
[ ] Yes
[x] No
If yes, please check if the following requirements are fulfilled
[ ] The Breaking Change or Deprecated label has been added
[ ] The migration steps are described in the following section
What changes might users need to make in their application due to this PR? (migration steps)
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
What kind of change does this PR introduce?
Bug fix: version was incorrect in file for new crac version.
What is the current behavior?
The retro compatibility test for v2.3 was called instead of the one for v2.4, no visible behavior change until someone need to add changes verifications v2.4 version.
What is the new behavior (if this is a feature change)? The retro compatibility test for v2.4 is called.
Does this PR introduce a breaking change or deprecate an API?
If yes, please check if the following requirements are fulfilled
What changes might users need to make in their application due to this PR? (migration steps)
Other information: