Upgrade PagibleAI CMS

PagibleAI CMS adheres to a semantic versioning scheme (SemVer) to provide a clear and predictable understanding of changes between releases. Our version numbers follow the MAJOR.MINOR.PATCH format, indicating the scope and impact of each update.

Release notes: https://github.com/aimeos/pagible/releases

Versioning Scheme

Major Releases (e.g., 1.0.0, 2.0.0)

Major releases introduce significant new features, architectural changes, or breaking changes that may require manual intervention during upgrades. These releases typically occur very seldom and are accompanied by comprehensive upgrade guides.

Minor Releases (e.g., 0.7.0, 1.1.0)

Minor releases contain new features and improvements that are backward-compatible. Upgrading between minor releases within the same major version (e.g., from 1.1.x to 1.2.x or 0.7.x to 0.8.x) is generally straightforward and should not introduce breaking changes.

Patch Releases (e.g., 0.7.1, 1.1.2)

Patch releases are reserved for bug fixes, security updates, and very minor improvements. These releases are always backward-compatible and are designed for immediate and effortless upgrades. Users are strongly encouraged to keep their installations updated with the latest patch releases.

Support Policy

PagibleAI CMS is committed to providing timely support and maintenance for its releases. Our support policy is designed to ensure stability and ease of upgrades for our users:

  • Minor-Release Support: Each minor release (e.g., 0.7.x, 0.8.x) will receive active support and critical bug fixes until the next minor release is published. For example, 0.7.x releases will be supported until 0.8.0 is released.
  • Patch Release Upgrades: Upgrading between patch releases (e.g., from 0.7.1 to 0.7.2 or 1.1.0 to 1.1.5) is designed to be immediate and effortless. Users can confidently upgrade to the latest minor versions as soon as they are available.
  • Security Updates: Security patches are backported to all currently supported mid-releases as quickly as possible.

Upgrade Guide

To upgrade your PagibleAI CMS installation, follow these general steps:

  1. Run composer update in your project's root directory.
  2. Run php artisan migrate to apply any database schema changes.
  3. Carefully check your configuration files for any newly added lines or changes. It is recommended to compare your config/cms.php file with the original provided in the new release.
  4. If you have customized any vendor templates in ./resources/views/vendor/cms/, compare your overwritten templates to the original ones to ensure compatibility and merge any necessary updates.
  5. Similarly, compare the CSS and JavaScript files located in ./public/vendor/cms/theme/ to the original files from the new release and merge any changes as required.
  6. Check the release notes for breaking changes.

We strongly recommend keeping your PagibleAI CMS installation updated to the latest available patch release within your current minor-release (e.g., 0.7.x) to benefit from bug fixes and security updates. When a new minor-release (e.g., 0.8.0) is published, we advise planning your upgrade accordingly to take advantage of new features and continued support.