Changelog

What has changed in RavenGrader. We list fixes as well as features. If we corrected something that affected your grades, you should be able to find out when.

RavenGrader is continuously deployed, so changes ship as they are ready rather than in numbered releases. Dates are when a change reached production.

July 2026

Grading accuracy

• Fixed several causes of incorrect scores: unit handling in final answers, multiple-choice questions scoring zero in some cases, and regrades running against a stale rubric after the rubric had been edited.
• Batch and instant grading now produce consistent results on the same submission. Previously the two paths could differ.
• Improved reading of hand-drawn diagrams and circuits, including questions where several different answers are equally correct. These are now assessed against the properties the answer must have rather than against a single example.
• Confidence flags are more reliable: flags now resolve correctly and failures that were previously silent are surfaced instead of disappearing.

Canvas integration

• Grade release is now retryable. Previously, if pushing a grade to the Canvas gradebook failed, the grade was still marked released, so the failure was permanent and invisible. Grades are now pushed first and marked released only on success, and failures are named and can be retried.
• Student resubmissions no longer overwrite reviewed work. A resubmission could previously clobber a submission you had already graded or that was mid-grading.
• Student feedback reports now return only student-facing fields. Instructor-side grading metadata is filtered server-side.
• Expired Canvas launches show a clear relaunch message instead of a broken page.
• Word (.docx) answer keys are accepted for Canvas assignments.

Rosters and student matching

• Students with the same name are no longer merged. Ambiguous roster matches are now flagged for you to assign manually rather than being guessed.

Uploads and file formats

• iPhone HEIC photos now convert reliably, including large batches.
• Password-protected PDFs and unsupported file types are rejected with a reason, rather than failing silently partway through.
• Fixed a race where files dropped in quick succession could be lost.
• The file picker and drag-and-drop now behave identically.

Reliability

• Submissions are no longer lost during a grading run, and cancelling now reports honestly what was and was not graded.
• Rubric generation survives a deployment mid-run, reconnects if the connection drops, and surfaces partial failures instead of appearing to hang.
• Bulk grading reports per-submission failures rather than only an overall state.

Billing

• Closed five paths that could over-charge page credits, and a case where cancelling a run could refund twice.

Transparency

• Published Terms of Service, a product documentation site, and a security page covering our practices and how to report a vulnerability.
• Corrected our Privacy Policy: one section understated what account deletion removes. Deleting an account removes uploaded files from storage as well as database records, and the policy now says so.
• Fixed our security and accessibility pages, which were redirecting visitors to a login page instead of loading.
• Shared feedback report links no longer require a join code. A link you send a student now simply works.

June 2026

• Sign in with Google.
• Fixed the submission viewer auto-scrolling to questions the student did not attempt.
• Improved rendering of mathematical notation in feedback.
• Fixed several subscription and billing-schedule edge cases.
• Bulk grading no longer picks up jobs with no live submissions.

Earlier

RavenGrader has been in active development since early 2026. This changelog begins in June 2026. We started keeping public notes at the point we had customers to keep them for, rather than reconstructing a history nobody was reading.

Something behaving differently from what you read here? Tell us, and if you have found a security issue, please use our disclosure policy instead.