Open edX Verawood: What's New and What Breaks

Most Open edX operators are about to discover their release-support clock has only four weeks left. Open edX Verawood, the 22nd community release, is scheduled to ship on June 9, 2026 — and the moment it lands, every release before it falls out of community support. That includes Ulmo, which most production sites only finished upgrading to a few months ago.

This article is the operator-side briefing on Verawood: the verified feature list, the deprecations you need to audit for, and a realistic 4–8 week upgrade methodology with honest time and cost ranges. We've shipped Open edX deployments at Cubite since 2013, across Sumac, Teak, Ulmo, and now Verawood — this is the same brief we'd hand our own engineering team.

The 30-Second Brief on Verawood

Open edX Verawood is the 22nd community release of the Open edX platform, scheduled for June 2026 (June 9 per the official Open edX release schedule). The code-cut window spans October 30, 2025 → April 9, 2026, per the Build-Test-Release proposal thread.

The release theme is platform maturity and operational stability — fewer flashy features, more long-term groundwork. Headline items:

• AI Extension Framework: the platform's first standardized AI integration spine
• Instructor Dashboard overhaul: migrating from Django templates to a modern React/Paragon MFE
• Stackable program pathways for credentials and curriculum chains
• LTI + Content Library hardening for reliable block-level reusability
• Frontend maturity: frontend-base (OEP-65), Paragon design tokens, tutor-contrib-paragon
• Improved Tutor + Kubernetes compatibility with reduced upgrade friction

The Open edX Release Calendar, Quickly Reframed

Open edX runs a six-month release cycle. Named versions ship every June 9 and December 9. Per the Open edX release schedule wiki:

Practical read: if you're not on Ulmo today, you're not just behind on features — you're running code with no upstream CVE coverage. If you are on Ulmo, your support window closes in about four weeks.

(Still weighing the platform itself rather than the upgrade? See our Open edX vs Moodle comparison before going further.)

What's Actually in Verawood — The Feature Deep Dive

Below are the Open edX Verawood features worth knowing as an operator. Every claim links to a primary source — docs.openedx.org, the openedx-ai-extensions repo, or the relevant GitHub deprecation issue.

The AI Extension Framework

The biggest strategic shift in Verawood is the . It's a platform plugin (openedx-ai-extensions) that introduces a standardized integration path for AI tools instead of the one-off bolt-ons that have characterized every Open edX AI integration since GPT-4.

Concretely, the framework provides:

• A LiteLLM-backed provider layer: supports OpenAI, Anthropic, and local models out of the box
• Tool primitives already shipped in the demo fixtures: content summarization, flashcard generation, chat with function calling, streaming chat, and an educator assistant
• MFE plugin slots in both the Learning MFE and the Authoring MFE for surfacing AI experiences to learners and authors
• Aspects event analytics so every AI workflow is observable
• Configuration-driven behavior: most setup happens in Django admin at /admin/openedx_ai_extensions/, not in code

The caveat that matters: per the project README, the framework is currently experimental and not yet recommended for production. What ships in Verawood is the infrastructure, not a polished product. Operators who set up the plugin pipeline now will be ready when first-party AI tools mature in subsequent releases — that's the win for early adopters.

The Instructor Dashboard MFE Migration

The Instructor Dashboard has been a server-rendered Django-template island in an otherwise MFE-first platform for years. Per GitHub issue #37214, that's changing — and the earliest breaking changes are unblocked in Verawood.

The new dashboard lives in frontend-app-instruct and is built on React, TypeScript, React Query, and Paragon. Ten-plus Django template files are targeted for removal, covering: course info, membership, cohort management, student administration, data downloads, special exams, certificates, and more.

If your deployment includes custom instructor flows or template overrides — and most multi-tenant or higher-ed deployments do — this is the single highest-impact deprecation in Verawood. Plan for a port, not a copy-paste. The deprecation timeline is still listed as TBD in the proposal, so the safe read is: Verawood is where the migration starts, not where it ends. Don't assume your overrides keep working through the full Verawood cycle.

Stackable Program Pathways

Verawood adds support for stackable pathways for programs — micro-credentials feeding into degrees, prerequisite chains, sequenced certifications. Until now, expressing real curriculum architecture in Open edX usually meant external workflow tools or custom XBlocks. With stackable pathways, the platform models that natively.

For higher-ed and workforce-credential operators, this is the most important content-architecture upgrade in two release cycles. For pure self-paced course catalogs, it's mostly invisible — and that's fine.

LTI + Content Library Hardening

Verawood builds on Ulmo's LTI Advantage Complete certification and reusable LTI configurations with two operator-grade improvements: reliable LTI block duplication (which has been historically brittle) and enhanced Content Library compatibility for block-level reusability. If you've ever lost a day debugging an LTI tool that worked in the source course but not in the duplicate, this is for you.

Frontend, Tutor, and Kubernetes

Verawood continues the maturation of — the unified modern frontend foundation specified in OEP-65. The companion tutor-contrib-paragon plugin handles compiling Paragon design tokens into MFE themes through Tutor, finally making Tutor-managed theming a first-class workflow instead of a brittle side path.

On the operations side, Verawood ships improved Tutor and Kubernetes compatibility and explicit work to reduce upgrade friction in the next cycle. Translation: this release pays you back at next upgrade, not this one.

What Breaks, Deprecates, and Disappears

The full Verawood breaking-change list is still being finalized in the Developer & Operator Release Notes — the source of truth on release day. The high-confidence list right now:

• Instructor Dashboard Django templates — ten-plus files targeted for removal as frontend-app-instruct lands (issue #37214). Audit any template overrides or instructor-tool customizations.
• Legacy frontend patterns predating frontend-base/OEP-65 — anything still hooking the pre-frontend-base scaffolding is on borrowed time.
• Paragon v22 patterns — if your theme code predates v23 design tokens, plan a port.
• Plugins not validated against the Ulmo-cycle Tutor changes — pip → uv and the Tutor Deck transition broke a long tail of community plugins. Anything you haven't smoke-tested under current Tutor is suspect.
• Aspects Analytics changes — consult the dev/op release notes when they finalize for any customizations on the analytics pipeline.

A plain Ulmo deployment with no forks and standard plugins will see a fairly mild Verawood. A heavily forked, multi-tenant, custom-instructor-dashboard deployment will not. Both deserve the audit; only one is allowed to skip the methodology below.

Why You Can't Just Wait

The cleanest argument for prioritizing your Open edX upgrade in 2026 is the support model itself. Per the Open edX release schedule, only the latest release receives community patches — and the community explicitly states it doesn't have capacity to support more than one release at a time.

Two compounding factors most operators underweight:

Operational debt compounds non-linearly. Each release you skip multiplies migration squashes, plugin breakages, and theme rewrites. The Open edX team periodically squashes Django migrations across versions, and selecting the right migration entry point is the difference between a clean upgrade and a corrupted database — as Raccoon Gang's upgrade guide puts it bluntly. Three skipped releases isn't 3× harder. It's closer to 6×.

EOL software is now a documented legal liability in the EU. The Cyber Resilience Act (CRA) makes vendors accountable for vulnerability handling in every component they ship — including end-of-life upstream open source. Per HeroDevs' analysis of the CRA, the regulation makes EOL software in your product stack a documented legal liability: you own the vulnerability-handling obligations for every component you ship, regardless of whether that component still has an upstream maintainer. If you serve learners in the EU, this isn't optional.

The defensible "wait for .1" position is real, but only if you're on Ulmo today. From Teak or earlier, every month of delay buys you more debt, not safety.

Why Most Teams Bring in a Partner (And What "Reliable" Looks Like)

Doing the Open edX upgrade in-house is viable. We've worked alongside teams who do it well. The shared traits are predictable: they upgrade more than once every 18 months, they have full-time staff fluent in Tutor / Django / MFEs, and their fork is small or vanilla.

If even one of those isn't true, the math usually tips toward a partner. A short DIY-vs-partner checklist:

What to look for in a partner:

• Verified Open edX provider status (listed on the Open edX Marketplace)
• A multi-release track record — ask specifically whether they shipped Sumac → Teak and Teak → Ulmo upgrades and what broke
• Transparent methodology and rollback policy — not just "we'll handle it"
• Real engineering depth — Tutor plugins, custom XBlocks, MFE work, not just managed hosting

Cubite has been engineering Open edX deployments since 2013. We offer dedicated Open edX hosting from $1,900/month, custom platform builds, and Verawood readiness assessments before the release ships. The methodology in this article is the same one our engineering team runs.

FAQ

What is Open edX Verawood?

Open edX Verawood is the 22nd community release of the Open edX platform, scheduled for June 2026. It focuses on platform maturity and modernization — introducing an AI Extension Framework, an MFE-based Instructor Dashboard, stackable program pathways, and improved Tutor / Kubernetes compatibility. It also marks the end of community support for the Ulmo release.

Verawood's code-cut window ran from October 30, 2025 to April 9, 2026. The release theme is operational stability over flashy features: most of the work is groundwork that pays back at the next upgrade — frontend-base maturity, reduced migration friction, hardened LTI duplication. See the official Verawood release notes for the canonical feature list.

When is Open edX Verawood released?

Open edX Verawood is scheduled to release on June 9, 2026, with code-cut completed in April 2026. It follows Open edX's six-month release cadence, succeeding Ulmo (December 2025). The moment Verawood ships, Ulmo loses community support — making the next four weeks the right window to plan and stage your upgrade.

The cadence is fixed: named releases drop every June 9 and December 9. Willow, the next release after Verawood, is planned for December 2026.

What's new in Open edX Verawood?

Verawood ships the AI Extension Framework (LiteLLM-powered, supporting OpenAI, Anthropic, and local models), a new MFE-based Instructor Dashboard built with React and Paragon, stackable program pathways, hardened LTI duplication and Content Library reusability, improved Tutor + Kubernetes compatibility, and Paragon design-token theme tooling via tutor-contrib-paragon.

The AI framework is the strategic headline; the Instructor Dashboard MFE migration is the practical one. If your deployment customizes the dashboard, that's where most of your Verawood engineering work will live.

Do I have to upgrade from Ulmo to Verawood?

Strictly, no — Open edX is open source. Practically, yes: only the latest release receives community security patches. The day Verawood ships, Ulmo joins Teak and Sumac in the unsupported tier, meaning every new CVE becomes your team's problem to backport. For most operators, planned upgrade beats unplanned incident response.

The EU Cyber Resilience Act adds a legal dimension: shipping EOL software to EU users carries documented vendor obligations. Combined with the operational-debt math (every skipped release roughly doubles upgrade complexity), the "wait" position only holds if you're on Ulmo and can afford to wait for Verawood's first patch release.

How long does an Open edX upgrade take?

A planned Ulmo to Verawood upgrade typically takes 4–8 weeks for a moderately customized instance: 1 week audit, 1–2 weeks fork reconciliation and plugin compatibility, 1–2 weeks staging build, 1 week dry-run migration with squashed Django migrations, and a weekend cutover with rollback gate. Heavily forked or multi-tenant deployments take longer.

Each release you've skipped roughly compounds the timeline. A Teak → Verawood upgrade isn't 2× harder than Ulmo → Verawood — it's more like 3–4× because of migration squashes, plugin compatibility gaps, and theme version drift.

Should I use a managed provider to upgrade Open edX?

If your team upgrades Open edX more often than once every 18 months and has staff fluent in Tutor, Django migrations, MFE builds, and your specific fork, in-house is viable. If not, an Open edX migration service provider almost always ships faster and safer — once you account for opportunity cost of internal engineering time.

The clearest signal: if you're more than one release behind (Teak or earlier) and you have any production customization, the risk profile strongly favors a partner.

Will my plugins break in Verawood?

Most actively maintained plugins ship Verawood-compatible versions in lockstep with the release. The breakages cluster in two places: plugins that haven't been updated through the Ulmo-cycle Tutor changes (pip → uv, Tutor Deck) and plugins that hook the legacy Instructor Dashboard templates. Both are findable in the plugin compatibility matrix phase of the upgrade methodology.

The forensic approach: for each plugin, check the latest release date, whether it has a Verawood-tagged version, and whether its issue tracker has open compatibility threads.

Is Open edX Verawood backward compatible with my current Tutor version?

Not always. Each Open edX named release pins to a major Tutor version, and Verawood continues the modernization that started in Ulmo (uv-based builds, Tutor Deck, tutor-contrib-paragon). Plan to bump Tutor as part of the upgrade — and validate every Tutor plugin against the new version before staging cutover.

The Tutor releases page is the canonical source; lock the Tutor version in your deployment manifest rather than tracking latest.

The Bottom Line

Open edX Verawood is the most consequential platform release in two years. The AI Extension Framework changes how AI integrations are built. The Instructor Dashboard MFE migration changes what every operator with custom instructor flows has to maintain. Stackable pathways change what's expressible as native curriculum architecture.

But the most actionable fact about Verawood isn't a feature. It's the date: June 9, 2026. The moment Verawood ships, Ulmo loses community support, Teak and Sumac sink deeper into unsupported territory, and the operational + legal cost of staying behind starts compounding faster.

The right move now isn't the upgrade itself — it's the pre-upgrade audit. Know your forks. Know your plugins. Know what your instructor dashboard customizations are about to cost you. Then plan the migration window with the methodology above.