Current Release and LTS Policy

Apostrophe 3: Join the Conversation

Apostrophe 3 is a major new release that makes developing and managing digital experiences with Apostrophe friendlier, faster, and more maintainable. Version 3.x is a Long Term Support release. If you want to skip the details and jump straight into the experience, check these links below:

Demo / Documentation / Source

Version 3.x emphasizes a modern frontend architecture for the administrative interface, powered by a library such as Vue. 3.x also emphasizes support for JavaScript promises even more than 2.x already does.

For more information, see our official announcement. As always, our community support is paramount and your input is welcome. Join the discussion on Github. 

Apostrophe 2.x is a long-term support release. 

We intend to provide full support for Apostrophe 2, which was released in 2016, until the end of 2023. In addition, maintenance will continue until at least the end of 2025 for those who wish to purchase an Apostrophe Enterprise Support SLA.

Apostrophe 0.5 was a previous release of Apostrophe for the node.js platform. We provided critical security fixes for Apostrophe 0.5 until September 1st, 2018. Maintenance remains available to those who wish to purchase an Apostrophe Enterprise Support SLA. Legacy documentation is available here.

Semantic versioning is a philosophy that says that each backwards-incompatible change should trigger a new major version number. It's a good policy because it makes it safe to use npm dependencies to install Apostrophe.

We will be following semantic versioning, with the following caveats:

We've begun with 2.0.0 to avoid confusion with an older PHP-based version of Apostrophe. In the future we will increment the major version number normally.

The addition of new option properties to the options object of a core Apostrophe type or module will not trigger a new major version number, which may impact you when extending modules. If you are concerned about conflicts, use a unique prefix for your own options.

The addition of new methods to a core Apostrophe type or module will not trigger a new major version number, which may impact you when extending modules. If you are concerned about conflicts, use a unique prefix for your own methods.

The addition of new, optional arguments to existing methods of core Apostrophe types or modules will not trigger a new major version number.

Also, just to be clear: bugs are bugs and may be fixed in a "patchlevel" release, no matter how used to them you may be. But, we'll aim to be reasonable about this.

The following are examples of things that would trigger a new major version number:

• Changing the arguments of an existing Apostrophe core method such that existing calls will fail.
• Removal of a core module (an Apostrophe module that ships with the `apostrophe` npm module).  

So set your npm dependencies to ^2.0.0 and follow the above advice to be safe.