#1058 introduce task versioning. Such information should be used when replaying tasks or verifying tasks with the task tester CI, hence the task version should be defined in the submission.
Teachers should also be able to replay a submission with the task version of their choice rather than the one defined in the submission. This could be useful when evaluation scripts are updated, i.e., the task version changes, and the teacher wants to re-evaluate some submissions.
Note that we do not provide backward compatibility guarantees. Breaking changes could be introduced between two task versions, hence a submission is only guaranteed to be re-playable with the task version with which it was produced.
#1058 introduce task versioning. Such information should be used when replaying tasks or verifying tasks with the task tester CI, hence the task version should be defined in the submission.
Teachers should also be able to replay a submission with the task version of their choice rather than the one defined in the submission. This could be useful when evaluation scripts are updated, i.e., the task version changes, and the teacher wants to re-evaluate some submissions.
Note that we do not provide backward compatibility guarantees. Breaking changes could be introduced between two task versions, hence a submission is only guaranteed to be re-playable with the task version with which it was produced.