1. Documentation
  2. Application
  3. PyroCMS
  4. Release Notes
Edit this Page

Release Notes

Versioning Scheme

PyroCMS, it's first-party addons, and the Streams Platform all maintain a Semantic Versioning convention: MAJOR.MINOR.MATCH

Patches may be released as often as every week. Patches will never contain breaking changes.

Minor releases will be released as communicated (usually every 4-6 months) and will also never contain breaking changes to standard installations but may require database migrations. Minor version changes may also contain small changes necessary to custom extensions or overridden configuration for example; however these changes will always be communicated through release notes.

When referencing the Streams Platform or addon packages from your composer.json, you should always use a version constraint such as ~1.6.*, since patches are safe and minor versions may include migrations.

Major releases are separated by years and represent fundamental shifts in the framework's architecture and/or conventions. Currently, there are no major version changes in development.

Support Policy

For LTS releases, such as PyroCMS v3.8, bug fixes are provided for 2 years and security fixes are provided for 3 years. These releases provide the longest window of support and maintenance. For general releases, bug fixes are provided for 6 months and security fixes are provided for 1 year. For all first-party addons, only the latest two releases receive bug fixes.

PyroCMS 3.9

PyroCMS 3.9 primarily addresses issues with Composer 2 and addon management. Core directory addons are now found in the vendor directory. The merge plugin has been removed as well.

Streams Platform 1.9

"anomaly/streams-platform": "~1.9.0",

Remove Dependencies

The following dependencies should be removed from your composer.json file.

  • wikimedia/composer-merge-plugin
  • anomaly/streams-composer-plugin