-
Notifications
You must be signed in to change notification settings - Fork 14
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
7e80af0
commit edc5b3a
Showing
1 changed file
with
5 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -29,15 +29,15 @@ To ensure a smooth transition, we recommend thorough testing of your application | |
All deprecations are listed below with the most recent announcements at the top. | ||
|
||
### 2024-12-02: Rerank v2.0 | ||
On December 2nd, 2024, we announced the release of Rerank-v3.5 along with the deprecation of the rerank-v2.0 model family. | ||
On December 2nd, 2024, we announced the release of Rerank-v3.5 along with the deprecation of the Rerank-v2.0 model family. | ||
|
||
| Shutdown Date| Deprecated Model| Deprecated Model Price| Recommended Replacement| | ||
|--------------|-----------------|-----------------------|------------------------| | ||
| 2025-03-31 | `rerank-english-v2.0` | $1.00 / 1K searches | `rerank-v3.5`| | ||
| 2025-03-31 | `rerank-multilingual-v2.0` | $1.00 / 1K searches | `rerank-v3.5`| | ||
|
||
# Best Practices: | ||
1.Regularly check our documentation for updates on announcements regarding the status of models. | ||
2.Test applications with newer models well before the shutdown date of your current model. | ||
3.Update any production code to use an active model as soon as possible. | ||
4.Contact [email protected] if you need any assistance with migration or have any questions. | ||
1. Regularly check our documentation for updates on announcements regarding the status of models. | ||
2. Test applications with newer models well before the shutdown date of your current model. | ||
3. Update any production code to use an active model as soon as possible. | ||
4. Contact [email protected] if you need any assistance with migration or have any questions. |