# Versioning policy

In order to integrate the appropriate LIFF SDK into your LIFF app, please make sure to understand the LIFF Versioning policy.

Note

By updating of LIFF SDK, the LIFF SDK integrated in your LIFF app may be discontinued. A LIFF app that uses the discontinued LIFF SDK cannot be opened.

If using the LIFF app for a long period of time, please check this page regularly and integrate the appropriate LIFF SDK.

# The LIFF MAJOR version status

The LIFF SDK life cycle is specified for each MAJOR version. The MAJOR versions of LIFF SDK currently supported and the status of each version are as follows:

LIFF Version
(Release date)
Status
(Period of current status)
Availability and description
LIFF v1
(June 6, 2018)
Maintaining
(~ April 2021)
✅ Bug fixes and security improvements needed to maintain existing features.
LIFF v2
(October 16, 2019)
Active
(~ Release date of the LIFF v3)
✅ The LIFF SDK is the current version. Frequently new features are added and existing features are improved.
LIFF v3
(TBD)

# The LIFF Versioning policy

Beginning with LIFF v2.2.0, the version number of LIFF will follow the rules set by Semantic Versioning (opens new window) (SemVer).

SemVer defines this version format:

MAJOR.MINOR.PATCH

For example, in v1.2.3, 1 is the MAJOR version, 2 is the MINOR version, and 3 is the PATCH version.

Here's what each version means:

Version Description
MAJOR It will be incremented if any backwards incompatible changes are introduced to the public API.
Example: v1.1.12 -> v2.0.0
MINOR It will be incremented if new, backwards compatible functionality is introduced to the public API.
Example: v1.1.12 -> v1.2.0
PATCH It will be incremented if only backwards compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
Example: v1.1.12 -> v1.1.13

# LIFF SDK (sdk.js) update policy

Since the LIFF v2.1.13 release, we prepare these two types of CDN paths. When Integrating the LIFF SDK into LIFF app, specify the CDN path that suits your purpose.

CDN path Description
CDN edge path This is a CDN path that contains only the MAJOR version. Use this CDN path if you want to always be up-to-date with the latest LIFF features. You only need to update your URL when a new MAJOR version is released.
e.g.: https://static.line-scdn.net/liff/edge/2/sdk.js
CDN fixed path This is a CDN path that contains up to the PATCH version. Use this CDN path if you want to use the LIFF features of a specific version. You can continue to use the specified PATCH version as long as you don't update the LIFF app. Update your URL only when you want to implement our new features, security updates, and bug fixes. It's not updated automatically and isn't affected by the LIFF SDK update.
e.g.: https://static.line-scdn.net/liff/edge/versions/2.1.13/sdk.js
Which version should you use?

Developers using the CDN fixed path will need to decide when to update their LIFF app. You can evaluate each update we provide by frequently checking the Release notes in the LIFF documentation and decide if the update is right for you.

Example of specifying a CDN edge path:

<script charset="utf-8" src="https://static.line-scdn.net/liff/edge/2/sdk.js"></script>
The CDN path to maintain backwards compatibility

In order to certify the behavior of the created LIFF app, we will continue to provide the LIFF SDK with the following CDN path. The LIFF SDK available with this CDN path is the same version as the LIFF SDK available with the CDN edge path.

CDN path for backwards compatibility:
https://static.line-scdn.net/liff/edge/2.1/sdk.js

Backwards compatible CDN path discontinuation

The CDN path to maintain backwards compatibility may be discontinued regardless of Life Cycle Schedule of the LIFF SDK. We recommend changing the CDN path specified in your LIFF app to the CDN edge path.

We will inform you as soon as the policy is decided.

# The LIFF SDK life cycle

The LIFF SDK life cycle is defined as follows for each MAJOR version.

The status is "Active" when a new MAJOR version is released. When the next MAJOR version is released, the status of the current MAJOR version will change from "active" to "maintenance" and after a period of time, it will change to "deprecated", then "obsolete".

Status Availability and description Support period
Active ✅ The LIFF SDK is the current version. Frequently new features are added and existing features are improved. From the release date of this MAJOR version to the release date of the next MAJOR version.
Maintaining ✅ Bug fixes and security improvements needed to maintain existing features. 12 months after "Active" period
Deprecated ✅ The LIFF SDK is no longer updated. 6 months after "Maintaining" period
End-of-life ❌ All CDN edge paths and CDN fixed paths will become invalid on the day we announce the EOL and the LIFF app will no longer be usable. -

# The LIFF SDK life cycle schedule

Familiarize yourself with the life cycle of MAJOR versions of the LIFF SDK and make the appropriate preparations.

LIFF Version
(Release date)
Active period Maintenance period Deprecation period End-of-life date
LIFF v1
(June 6, 2018)
~ October 15, 2019
✅ LIFF v1
~ April 2021
✅ LIFF v1
~ September 2021
✅ LIFF v1
September 2021
❌ LIFF v1
LIFF v2
(October 16, 2019)
~ Release date of the LIFF v3
✅ LIFF v2
~ TBD
✅ LIFF v2
~ TBD
✅ LIFF v2
TBD
❌ LIFF v2
LIFF v3
(TBD)

✅ LIFF v1/❌ LIFF v1: Availability of https://d.line-scdn.net/liff/1.0/sdk.js

✅ LIFF v2/❌ LIFF v2: Availability of https://static.line-scdn.net/liff/edge/2/sdk.js, https://static.line-scdn.net/liff/edge/versions/2.x.x/sdk.js, and https://static.line-scdn.net/liff/edge/2.1/sdk.js

Note
  • The maintenance period for LIFF v1 has been extended beyond the standard to give developers more time to prepare for the switch, because there were periods when the versioning policy and life cycle schedule were not specified. Similarly, the deprecation period and end-of-life date for LIFF v1 have changed.
  • The life cycle schedule is subject to change.