Wheels 4.0 feature audit — 260+ PRs catalogued by subsystem

[bpamiri]

As part of the 4.0 release prep I've compiled a full inventory of every user-visible change merged to develop since the 3.0.0 release. The goal is a single place to answer "what actually ships in 4.0" with PR-level receipts instead of marketing copy.

Summary stats

• 260+ merged PRs across roughly 15 weeks (3.0.0 → today)
• ~70 distinct user-visible features / changes after deduplicating multi-PR features
• 40+ security-hardening PRs — a full section in the audit
• 7 breaking changes — each covered in the upgrade guide with a consistent detect / fix / opt-out structure
• Contributors: @bpamiri, @zainforbjs, @chapmandu, @mlibbe, @MukundaKatta, plus dependabot

Subsystems covered

The audit buckets every PR into 22 categories including ORM & data layer, migrations, routing, controllers, views, middleware pipeline, background jobs, SSE, multi-tenancy, DI container, packages, testing infrastructure, CLI + LuCLI, MCP, engine adapters, and security hardening. Each category lists every PR with a one-line description and link.

How the doc was produced

1. gh pr list --base develop --state merged --search "merged:>=2026-01-10" for the raw PR set.
2. Cross-referenced against git log --merges v3.0.0+33..origin/develop.
3. Compared against the [Unreleased] section of CHANGELOG.md (which had ~60 gaps — addressed by a separate catch-up PR).
4. Grouped multi-PR features into single entries with all PR links.

Links

• Full audit (docs/releases/wheels-4.0-audit.md)
• 3.0 → 4.0 comparison (derived from the audit)
• docs/wheels-vs-frameworks.md (peer-framework parity)
• Upgrade guide

Question for the thread

If you spot a user-visible change that isn't in the audit or find a bucket where something is miscategorized, please comment or open an issue. The audit is meant to be the source of truth for release-comms, so corrections before GA are especially welcome.

[zain4bjs]

This has been a major milestone, one of the most significant achievements for any framework within a span of just three months. Kudos to @bpamiri for the dedication and efforts.

Teamwork truly makes the dream work 🚀

[mikegrogan]

Nice job Peter!

[bpamiri]

Thank you everyone. My dream since my early involvement with Wheels (CFWheels at that time) was to make the language irrelevant and bring the functionality of the framework in line with other frameworks. I've said this a hundred times, people weren't Ruby developers before Rails came along and made web development so much easier that people learned Ruby to use Rails. That's the way I look at Wheels. It should be so good that none CFML developers will learn CFML in order to use Wheels. That is why we are comparing against Rails, Laravel, and Django. Porting features over and shrinking the gap.

[zain4bjs]

ofcause, Good Luck 🤞