Skip to content

Commit 67e4e4e

Browse files
oliwiapolecoliwiapolec
authored
Deprecate 3.3 APIs (#1559)
1 parent 4df0ad7 commit 67e4e4e

File tree

10 files changed

+25
-25
lines changed

10 files changed

+25
-25
lines changed

‎src/constants/index.js‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
const VERSIONS_GROUPS = {
22
DEFAULT: {
33
STABLE_VERSION: "3.5",
4-
LEGACY_VERSIONS: ["3.3", "3.4"],
4+
LEGACY_VERSIONS: ["3.4"],
55
DEV_PREVIEW_VERSION: "3.6",
6-
DEPRECATED_VERSIONS: [],
6+
DEPRECATED_VERSIONS: ["3.3"],
77
ALL_VERSIONS: ["3.6", "3.5", "3.4", "3.3"],
88
},
99
"chat-widget": {
@@ -15,9 +15,9 @@ const VERSIONS_GROUPS = {
1515
},
1616
"data-reporting": {
1717
STABLE_VERSION: "3.5",
18-
LEGACY_VERSIONS: ["2.0", "3.3", "3.4"],
18+
LEGACY_VERSIONS: ["2.0", "3.4"],
1919
DEV_PREVIEW_VERSION: "3.6",
20-
DEPRECATED_VERSIONS: [],
20+
DEPRECATED_VERSIONS: ["3.3"],
2121
ALL_VERSIONS: ["3.6", "3.5", "3.4", "3.3", "2.0"],
2222
},
2323
"customer-accounts-api": {

‎src/pages/data-reporting/index.mdx‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -46,12 +46,12 @@ Log errors and monitor the performance of your application.
4646

4747
The Reports API goes through several stages in its lifecycle.
4848

49-
| | |
50-
| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
49+
| | |
50+
| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
5151
| **dev preview** | It gives a preview of the features that are currently in development. **It's subject to change and comes with limited access**. Contact us at [email protected] or <a href="#open-chat" onClick={openChatWindow}>ask on the chat</a> to get access. Lasts for ~6-7 months. |
52-
| **stable** | It has a closed feature set and is publicly available. It receives all bug fixes. Lasts for ~6-7 months. |
53-
| **legacy** | We're gradually dropping support for this version. It receives only critical and security bug fixes. Lasts for ~1-1.5 year. Responses contain the `Legacy` header that specifies when this stage ends (in the `YYYY-MM-DD` format). |
54-
| **deprecated** | It receives only critical and security bug fixes. Lasts for 6 months before it's decommissioned. Responses contain the `Deprecation` header that specifies when this stage ends (in the `YYYY-MM-DD` format). |
52+
| **stable** | It has a closed feature set and is publicly available. It receives all bug fixes. Lasts for ~6-7 months. |
53+
| **legacy** | We're gradually dropping support for this version. It receives only critical and security bug fixes. Lasts for ~1-1.5 year. Responses contain the `Legacy` header that specifies when this stage ends (in the `YYYY-MM-DD` format). |
54+
| **deprecated** | It receives only critical and security bug fixes. Lasts for ~3-6 months before it's decommissioned. Responses contain the `Deprecation` header that specifies when this stage ends (in the `YYYY-MM-DD` format). |
5555

5656
<img
5757
alt="Reporting API lifecycle"

‎src/pages/data-reporting/reports-api/v3.3/index.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Reports API allows you to **access** and **extract** all the [Reports](https://w
1616

1717
## Versioning
1818

19-
This document describes the **LiveChat Reports API v3.3**, which is a legacy version. For production-ready applications, it's best to use to the current stable version. [Read more about versioning...](/data-reporting/#api-versioning)
19+
This document describes the **LiveChat Reports API v3.3**. This is the **deprecated** version. For production-ready applications, it's best to use to the current stable version. [Read more about versioning...](/data-reporting/#api-versioning)
2020

2121
### Lifecycle headers
2222

‎src/pages/management/configuration-api/v3.3/index.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Configuration API is a service for storing configuration of license. You can set
1616

1717
## Versioning
1818

19-
This document describes the **Configuration API v3.3**, which is a legacy version. For production-ready applications, it's best to use to the current stable version. [Read more about versioning...](/management/#api-versioning)
19+
This document describes the **Configuration API v3.3**. This is the **deprecated** version. For production-ready applications, it's best to use to the current stable version. [Read more about versioning...](/management/#api-versioning)
2020

2121
### Lifecycle headers
2222

‎src/pages/management/index.mdx‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -24,12 +24,12 @@ Here are some of the most common use cases of the Configuration API:
2424

2525
The LiveChat Configuration API goes through several stages in its lifecycle.
2626

27-
| | |
28-
| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
27+
| | |
28+
| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
2929
| **dev preview** | It gives a preview of the features that are currently in development. **It's subject to change and comes with limited access**. Contact us at [email protected] or <a href="#open-chat" onClick={openChatWindow}>ask on the chat</a> to get access. Lasts for ~6-7 months. |
30-
| **stable** | It has a closed feature set and is publicly available. It receives all bug fixes. Lasts for ~6-7 months. |
31-
| **legacy** | We're gradually dropping support for this version. It receives only critical and security bug fixes. Lasts for ~1-1.5 years. Responses contain the `Legacy` header that specifies when this stage ends (in the `YYYY-MM-DD` format). |
32-
| **deprecated** | It receives only critical and security bug fixes. Lasts for 6 months before it's decommissioned. Responses contain the `Deprecation` header that specifies when this stage ends (in the `YYYY-MM-DD` format). |
30+
| **stable** | It has a closed feature set and is publicly available. It receives all bug fixes. Lasts for ~6-7 months. |
31+
| **legacy** | We're gradually dropping support for this version. It receives only critical and security bug fixes. Lasts for ~1-1.5 years. Responses contain the `Legacy` header that specifies when this stage ends (in the `YYYY-MM-DD` format). |
32+
| **deprecated** | It receives only critical and security bug fixes. Lasts for ~3-6 months before it's decommissioned. Responses contain the `Deprecation` header that specifies when this stage ends (in the `YYYY-MM-DD` format). |
3333

3434
<img
3535
alt="Configuration API lifecycle"

‎src/pages/messaging/agent-chat-api/v3.3/index.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ robots: "noindex"
1313

1414
## Versioning
1515

16-
This document describes the **Agent Chat Web API v3.3**, which is a legacy version. For production-ready applications, it's best to use to the current stable version. [Read more about versioning...](/messaging/#api-versioning)
16+
This document describes the **Agent Chat Web API v3.3**. This is the **deprecated** version. For production-ready applications, it's best to use to the current stable version. [Read more about versioning...](/messaging/#api-versioning)
1717

1818
### Lifecycle headers
1919

‎src/pages/messaging/agent-chat-api/v3.3/rtm-reference/index.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ robots: "noindex"
1313

1414
## Versioning
1515

16-
This documentation describes the **Agent Chat Real-Time Messaging API v3.3**, which is a legacy versions. For production-ready applications, it's best to use to the current stable version. [Read more about versioning...](/messaging/#api-versioning)
16+
This documentation describes the **Agent Chat Real-Time Messaging API v3.3**. This is the **deprecated** version. For production-ready applications, it's best to use to the current stable version. [Read more about versioning...](/messaging/#api-versioning)
1717

1818
### Lifecycle headers
1919

‎src/pages/messaging/customer-chat-api/v3.3/index.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ robots: "noindex"
1313

1414
## Versioning
1515

16-
This document describes the **Customer Chat Web API v3.3**, which is a legacy versions. For production-ready applications, it's best to use to the current stable version. [Read more about versioning...](/messaging/#api-versioning)
16+
This document describes the **Customer Chat Web API v3.3**. This is the **deprecated** version. For production-ready applications, it's best to use to the current stable version. [Read more about versioning...](/messaging/#api-versioning)
1717

1818
### Lifecycle headers
1919

‎src/pages/messaging/customer-chat-api/v3.3/rtm-reference/index.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ robots: "noindex"
1313

1414
## Versioning
1515

16-
This document describes the **Customer Chat Real-Time Messaging API v3.3**, which is a legacy versions. For production-ready applications, it's best to use to the current stable version. [Read more about versioning...](/messaging/#api-versioning)
16+
This document describes the **Customer Chat Real-Time Messaging API v3.3**. This is the **deprecated** version. For production-ready applications, it's best to use to the current stable version. [Read more about versioning...](/messaging/#api-versioning)
1717

1818
### Lifecycle headers
1919

‎src/pages/messaging/index.mdx‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -20,12 +20,12 @@ This document gives you an overview of the LiveChat messaging protocol, explaini
2020

2121
The LiveChat Messaging APIs go through several stages in their lifecycle.
2222

23-
| | |
24-
| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
23+
| | |
24+
| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
2525
| **dev preview** | It gives a preview of the features that are currently in development. **It's subject to change and comes with limited access**. Contact us at [email protected] or <a href="#open-chat" onClick={openChatWindow}>ask on the chat</a> to get access. Lasts for ~6-7 months. |
26-
| **stable** | It has a closed feature set and is publicly available. It receives all bug fixes. Lasts for ~6-7 months. |
27-
| **legacy** | We're gradually dropping support for this version. It receives only critical and security bug fixes. Lasts for ~1-1.5 years. Responses contain the `Legacy` header that specifies when this stage ends (in the `YYYY-MM-DD` format). |
28-
| **deprecated** | It receives only critical and security bug fixes. Lasts for 6 months before it's decommissioned. Responses contain the `Deprecation` header that specifies when this stage ends (in the `YYYY-MM-DD` format). |
26+
| **stable** | It has a closed feature set and is publicly available. It receives all bug fixes. Lasts for ~6-7 months. |
27+
| **legacy** | We're gradually dropping support for this version. It receives only critical and security bug fixes. Lasts for ~1-1.5 years. Responses contain the `Legacy` header that specifies when this stage ends (in the `YYYY-MM-DD` format). |
28+
| **deprecated** | It receives only critical and security bug fixes. Lasts for ~3-6 months before it's decommissioned. Responses contain the `Deprecation` header that specifies when this stage ends (in the `YYYY-MM-DD` format). |
2929

3030
<img
3131
alt="Messaging API lifecycle"

0 commit comments

Comments
 (0)