From c362bcf9309fa2f248db6ff549cb98f58ab6e8d2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Miroslav=20Bajto=C5=A1?= Date: Wed, 3 Mar 2021 09:22:29 +0100 Subject: [PATCH] docs: end of life MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit LB3 has reached end of life and this connector does not support LB4. Signed-off-by: Miroslav Bajtoš --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md b/README.md index 5431c5e..86822fd 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,14 @@ # loopback-connector-remote +**THIS CONNECTOR DOES NOT SUPPORT LOOPBACK 4** + +**⚠️ LoopBack 3 has reached end of life. We are no longer accepting pull requests or providing +support for community users. The only exception is fixes for critical bugs and security +vulnerabilities provided as part of support for IBM API Connect customers. +We urge all LoopBack 3 users to migrate their applications to LoopBack 4 as soon as possible. +Learn more about +LoopBack's long term support policy.** + The remote connector enables you to use a LoopBack application as a data source via REST. You can use the remote connector with a LoopBack application, a Node application, or a browser-based application that uses [LoopBack in the client](LoopBack-in-the-client.html). The connector uses [Strong Remoting](Strong-Remoting.html). @@ -7,6 +16,7 @@ The connector uses [Strong Remoting](Strong-Remoting.html). In general, using the remote connector is more convenient than calling into REST API, and enables you to switch the transport later if you need to. Use loopback-connector-remote: + - Version 3.x with LoopBack v3 and later. - Prior versions with LoopBack v2.