Every finding starts with a citation you can open.
Release notes, changelogs, deprecation notices and version diffs — captured with dates, so you can judge the change yourself instead of trusting a summary.
Now open — create an account and connect your first course.
TeachCurrent helps software educators maintain existing courses. We track the tools and frameworks you teach, show the source evidence behind every change, point to the lessons it affects, and draft the update for your review.
Every suggestion links back to its source. Read our evidence standard.
React 19.2 release notes
New `use` hook guidance replaces the manual promise pattern.
Module 4 · Lesson 12 — Data fetching
Two code samples and one slide reference the removed pattern.
Rewrite sample + slide callout
Draft replacement prepared for your approval.
Release notes, changelogs, deprecation notices and version diffs — captured with dates, so you can judge the change yourself instead of trusting a summary.
Modules, lessons, code samples and slides — listed by where the change lands.
Nothing is published for you. Suggestions stay drafts until an instructor signs off.
Each finding carries an explicit state — confirmed, needs review, or action required — so incomplete analysis is never presented as a finished result.
Point TeachCurrent at your existing modules, lessons and code samples, and name the tools and versions you teach.
We monitor releases and deprecations for those dependencies and record the evidence for each change.
You get the affected lessons and a suggested edit for each one. You approve, adjust, or dismiss.
Every finding connects a passage in your lesson transcript to the documentation used for the comparison. You review the evidence and decide whether the lesson needs an update.
A repeatable workflow from version baseline to recorded decision.
Read the guideThe columns to record, and how to decide update, keep or retire.
Read the guideScope, verify and plan the smallest fix that unblocks students.
Read the guide