Publishing Patches vs New Revisions

Fixing a typo shouldn’t force every learner to start over. Patch the small stuff; only bump the revision when the course truly changes shape.

Authors should be able to fix a typo without forcing every learner to restart. We separated light patches from true structural revisions so progress stays intact when the course shape has not changed—and everyone restarts only when it must.

Patch by default for small edits — Publish with a short description of what changed. Keep the same revision for minor in-place updates so progress can stay intact.
New revision when structure changes — Incrementing the revision (or when Skillhabit locks it on) covers bigger structural changes and may require learners to restart—because the path they were on is no longer the same course.
Clear structural triggers — Element IDs and order, chapter structure, question choice IDs, and passing criteria can force a revision bump, so you are not guessing what counts as “big.”
Optional force reset — Independently reset existing results when you need a clean slate—even if the revision story alone would not.