Backend Development 2 min read

CodeIgniter 4.3.0 Release Notes and Upgrade Guide

The announcement details CodeIgniter version 4.3.0, highlighting over 50 enhancements, important breaking changes, required updates to the spark executable and configuration files, and provides links to the changelog and upgrade guide for developers to safely migrate their applications.

Laravel Tech Community
Laravel Tech Community
Laravel Tech Community
CodeIgniter 4.3.0 Release Notes and Upgrade Guide

We thank the team and many contributors for releasing version 4.3.0, which includes numerous enhancements.

Unfortunately, there are some major changes, so upgrades should be performed cautiously; please read the changelog and upgrade guide thoroughly.

You must update the spark executable and several configuration files.

Most existing applications require no further intervention unless you use custom classes that extend framework classes.

Some default values in configuration files have changed; existing applications are generally unaffected unless you have modified those values yourself.

This version contains more than 50 enhancements, with the most important being:

Query Builder now supports upsert() , upsertBatch() , deleteBatch() , and the batch() method can set data directly from a query.

Database Forge can add indexes and named indexes to existing tables.

The "spark route" command has been enhanced.

Improvements to CLI command testing.

Enhancements to View Cells.

You can view the full list of enhancements in the changelog.

Changelog: https://www.codeigniter.com/user_guide/changelogs/v4.3.0.html Upgrade guide: https://www.codeigniter.com/user_guide/installation/upgrade_430.html

backend developmentPHPreleaseUpgradeframeworkCodeIgniter
Laravel Tech Community
Written by

Laravel Tech Community

Specializing in Laravel development, we continuously publish fresh content and grow alongside the elegant, stable Laravel framework.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.