Change parsec version to 1.3.0

Signed-off-by: Tomás González <tomasagustin.gonzalezorlando@arm.com>
tgonzalezorlandoarm · Oct 25, 2023 · 8108f7b · 8108f7b
1 parent 200a8c2
commit 8108f7b
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/src/parsec_service/build_run.md b/src/parsec_service/build_run.md
@@ -36,7 +36,7 @@ at `/tmp/parsec.sock`. The test configuration will make those choices.
 Clone the Parsec service repo,
 
 ```
-git clone --branch 1.2.0 https://github.com/parallaxsecond/parsec.git
+git clone --branch 1.3.0 https://github.com/parallaxsecond/parsec.git
 ```
 
 Having cloned the Parsec repository, to build and run from source using the Mbed Crypto provider and

diff --git a/src/parsec_service/stability.md b/src/parsec_service/stability.md
@@ -23,7 +23,7 @@ without breaking anything. The only exception is for the communication channel w
 any version of the client library can successfully communicate with any version of the service.
 
 The principle of [semantic versioning](https://semver.org/) is used to describe the stability of
-Parsec versions and when breaking changes are done. If `parsec` version is at `1.2.0` then all
+Parsec versions and when breaking changes are done. If `parsec` version is at `1.3.0` then all
 future stable version to that will be `1.x.y`. Note that, although semver is used to describe Parsec
 stability, it is a strong goal for Parsec to remain stable at a `1.x.y` version. This document
 introduces the efforts that are made so that a `MAJOR` version bump should hopefully never happen.