Skip to main content
Capell home
Live demo

What's New is the short, readable account of shipped Capell work. It adds audience and action context to the exact version history kept in the changelog.

Each entry answers

  • What became available?
  • Who is affected?
  • Is any upgrade, migration, package review, or documentation change needed?
  • Where is the complete release detail?

Ideas and unfinished work belong on the roadmap. Experience from a named contributor belongs in Field Notes.

What's New

What shipped, in plain language.

Read the notable changes with dates, affected roles, and links to the Core and Packages release records.

Read Core's release notes on GitHub Read Capell Packages release notes on GitHub
Capell release stages, health evidence, cache state, audit history, and rollback controls arranged on an operations desk.
Capell updates

Get the useful release notes by email.

An occasional digest of shipped changes, upgrade checks, and Field Notes. There is no fixed send schedule.

Release

Capell 1.0.35 foundation released

Capell 1.0.35 is now available as a tested lockstep foundation release.

Capell Release Foundation

Capell 1.0.35 is now available as a tested lockstep foundation release. The full changelog and upgrade guide contain the exact package and compatibility details for this release.

Read the release notes and review the upgrade guide.

Release

Capell 1.0.34 foundation released

Capell 1.0.34 is now available as a tested lockstep foundation release.

Capell Release Foundation

Capell 1.0.34 is now available as a tested lockstep foundation release. The full changelog and upgrade guide contain the exact package and compatibility details for this release.

Read the release notes and review the upgrade guide.

Release Featured

Capell 1.0.2 foundation released

Core, Admin, Frontend, Installer, and Marketplace now ship as one lockstep compatibility release.

Capell Release Foundation

Capell 1.0.2 publishes Core, Admin, Frontend, Installer, and Marketplace at one shared version. Their internal Composer requirements now follow that release version, so a project resolves a tested foundation set instead of mixing package generations.

Improvement

Fresh Capell installation path verified

The public 1.0.2 packages now complete installation, asset setup, health checks, and first-page delivery in a clean Laravel application.

Installer Laravel Verification

The Capell 1.0.2 installer completes package discovery and lifecycle work in fresh processes, builds the frontend assets, and performs its final health check against the completed application. Two independent Laravel 13 installations resolved the public tags and returned the homepage and admin login successfully.

Fix

Filament panel setup now includes the Capell theme entrypoint

New Capell admin panels now scaffold the theme file expected by the generated Vite configuration.

Admin Filament Vite

Creating a Capell Filament panel now writes the matching admin theme entrypoint before the first frontend build. The generated Vite inputs and the application filesystem therefore agree on a fresh installation.

The release action is clear

Most updates do not require every reader to do the same thing. Maintainers may need an upgrade check, editors may need a workflow note, and buyers may only need to know that a package is now ready to inspect.

Use the linked record that owns the detail instead of treating a product highlight as installation guidance or a promise about future work.

Check the exact version Use Capell Core's GitHub releases for exact version numbers and the complete Core release sequence. Open Core's releases
Check package release notes Use Capell Packages' GitHub releases for the companion-package release sequence. Check an individual marketplace listing before adoption. Open Capell Packages releases
Prepare the version change If the release affects an active application, review compatibility, stage the change, run the relevant checks, and keep a recovery path ready. Plan the upgrade
Keep future work separate A roadmap item can be open, planned, or in progress without being available. Depend on the shipped record when planning a live project. Check roadmap status
Loading footer