Versioning policy

The current version of Components is v37.4.3. CSS is at v10.0.5. Dynamic Flows is at v15.2.4.

Our goal is to ensure all our consumers understand when and how new features are added, and to be well-prepared when we remove features or make breaking changes.

We understand you need stability from Neptune Web, and are working towards less and less frequent breaking changes. We appreciate your patience while we get there.

Versioning

We follow SemVer. Please note that we do not bump versions for changes to the internal implementation of components.

We only support the latest version of Neptune Web, and do not backport any changes to older versions.

Deprecation

In the event of a planned breaking change, we will add warnings in the console (in development only) to indicate that a feature in use is scheduled for deprecation, and will provide migration instructions.

In general, the feature will be removed in the next major version, but we will provide advice if the time period is known to be different from this.

Release schedule

Currently we release at most one major release per month. We hope to reduce the frequency of major releases further over the coming months, as the library stabilises.

The core team will generally release a minor release once per fortnight, with patch releases when required.

Because we accept contributions at all times, extra minor releases may happen when new features are contributed.

Relationship between packages

We have some inter-package dependencies that cause one version to be bumped when its dependency is updated. Because Components depends on CSS, when we release a new CSS build, we will update the dependency and release a new Components build. The same goes for Dynamic Flows, which has a dependency on Components.

Edit these docs on Github