-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
None
-
Future Sustainability
-
False
-
-
False
-
5
-
None
-
None
-
uShift Sprint 271, uShift Sprint 272, uShift Sprint 273
The file needs to be updated several time during the release and we often forget about it and run out dated tests.
I think we should automate updating the file. At least have a script that updates the file, later we could make it part of rebase.
We also need to think about previous branches where that file started appearing.
We could use functions we had in 4.16 or 4.17 as starting point. They were dynamically resolving the versions at runtime