EOS-5 release 5.1.23 contains the 0-sized files fix, but is missing the --no-workflow fix... This fix will only be included in the next tagged release (probably 5.2.0).
This release 5.2.0 will also include other EOS-CTA fixes which are not meant to be included in EOS-4 (considering that EOS-4 is being deprecated...), such as:
#278 (closed): Modifications to eos evict/stagerrm command
#210 (closed): [EOS] Modify STAGE polling (GET) logic to take into account files not queued on CTA
#389 (closed): Add a MGM configuration entry to override the URI returned by the .well-known Tape REST API
#390 (closed): HTTP TAPE REST bulk prepare attributes when file does not exist
Considering this, I suggest that we wait for 5.2.0 to be tagged before changing versionlock.list and tagging the next CTA release (as long as the tagging of 5.2.0 does not take too long).
This allows us to include the --no-workflow fix in EOS-5, which is a requirement for the file migration scripts developed by @lwardena . It also allows us to cover in our CI the other EOS-5 changes.