From 3c7080c49f7921beaf559fbb6c8a13f272502025 Mon Sep 17 00:00:00 2001
From: Ludovic Robert <30499179+bigludo7@users.noreply.github.com>
Date: Tue, 16 Jul 2024 20:37:19 +0200
Subject: [PATCH] Update one-time-password-sms yaml  version to 1.0.0-rc.1

---
 code/API_definitions/one-time-password-sms.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/code/API_definitions/one-time-password-sms.yaml b/code/API_definitions/one-time-password-sms.yaml
index 8c0c242..5d70085 100644
--- a/code/API_definitions/one-time-password-sms.yaml
+++ b/code/API_definitions/one-time-password-sms.yaml
@@ -21,7 +21,7 @@ info:
 
     It is important to remark that in cases where personal user data is processed by the API, and users can exercise their rights through mechanisms such as opt-in and/or opt-out, the use of 3-legged access tokens becomes mandatory. This measure ensures that the API remains in strict compliance with user privacy preferences and regulatory obligations, upholding the principles of transparency and user-centric data control.
 
-  version: wip
+  version: 1.0.0-rc.1
   termsOfService: http://example.com/terms/
   contact:
     name: API Support