# LWC Versioning

LWC open-source (OSS) follows a version number using the major.minor.patch pattern. It adheres to semantic versioning (semver) characteristics.

• Patch release updates that include non-critical fixes or internal code refactors correspond to an increment to the patch number like v2.49.0 to v2.49.1.
• New features and minor fixes correspond to an increment to the minor number like v2.49.1 to v2.50.0.
• Breaking changes correspond to an increment to the major number like v2.50.0 to v3.0.0.

We release breaking changes to LWC OSS independent of the Salesforce release schedule. A major version increment also corresponds with a new API version as it introduces breaking changes for off-core components. When the LWC dependency is updated, on-core components for internal Salesforce developers use the next version automatically.

# Breaking Changes

The LWC framework prides itself on backwards compatibility, and we strive to avoid breaking your code when shipping a new release. Versioning allows us to ship new features, bug fixes, or performance improvements while also allowing us to deprecate legacy features.

Here are the breaking changes.

• v8.0.0
• v7.0.0
• v6.0.0
• v5.0.0
• v4.0.0
• v3.0.0
• v2.0.0

# Minor Releases

Minor releases typically include new features, minor fixes, and performance updates.

See LWC releases.

# Component-Level API Versioning

For LWC OSS, the API version on the component is always the latest version that corresponds to the LWC framework version.

From Winter'24, custom components for the Salesforce platform are versioned. Component-level API versioning informs the LWC framework to behave as it did for the Salesforce release corresponding to the API version for that component.

Component-level API versioning is determined by the apiVersion value on the component's *.js-meta.xml file. If an apiVersion value isn't provided, LWC defaults to the latest version. API versioning on a component is scoped to a component definition and its dependence on the version of the LWC framework. Every HTML, CSS, and JS file on a component corresponds to one API version.

To see what's changed in LWC in the latest Salesforce release that apply to all apiVersion values, see the Salesforce release notes.

# Salesforce Lightning Platform Versioning

LWC OSS versioning maps to versioning on the Salesforce platform.

* API version 60.0 also includes changes from LWC OSS v4.0.0.