Course Versioning: What is the best practice?

Scenario: We have a SCORM course, “Cybersecurity Awareness”.  We update the course annually so in our old LMS we would publish a “Cybersecurity Awareness 2017”, “Cybersecurity Awareness 2018”, “Cybersecurity Awareness 2019” and so on.  This way on the report we would know what version of the course the learner completed.

Options

1. Publish one SCORM course, “Cybersecurity Awareness” and annually update the SCORM package and set the SCORM Enrollment Migration Options: “Move enrollments when completed and a new course version exists”
2. Publish one SCORM course and annually change the title to reflect version changes, “Cybersecurity Awareness 2018.1” and set the SCORM Enrollment Migration Options: “Move enrollments when completed and a new course version exists”
3. Publish a new SCORM course for every version “Cybersecurity Awareness 2020”, “Cybersecurity Awareness 2021”, “Cybersecurity Awareness 2022”
4. SOME OTHER SCHEME