We released the LIFF Versioning policy to clarify the purpose of each version of LIFF. We've also released the life cycle of each MAJOR version so that developers can make appropriate preparations for the version upgrade of LIFF.
# The LIFF Versioning policy
Beginning with LIFF v2.2.0, the version number of LIFF will follow the rules set by Semantic Versioning (SemVer).
SemVer defines this version format:
For example, in
1 is the MAJOR version,
2 is the MINOR version, and
3 is the PATCH version.
The LIFF Versioning policy also explains the life cycle of the MAJOR version and provides an explanation for what each version (MAJOR, MINOR, PATCH) means for developers.
# 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 edge path||This is a method to specify only the MAJOR version. You can always use the new version of the LIFF SDK without updating your LIFF app.|
|CDN fixed path||This is a method to specify up to the PATCH version. You can continue to use the specified PATCH version as long as you don't update the LIFF app. It is not updated automatically and is not affected by the LIFF SDK update. |
Example of specifying a CDN edge path:
<script charset="utf-8" src="https://static.line-scdn.net/liff/edge/2/sdk.js"></script>
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:
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.
Learn more about the LIFF Versioning policy in the LIFF documentation.