docs: Update versions to Serenity 5.3.0

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: wakaleo

docs/cucumber/cucumber-junit5.md

@@ -32,7 +32,7 @@ Add the following dependencies to your `pom.xml`:
 
 ```xml
 <properties>
-    <serenity.version>5.2.4</serenity.version>
+    <serenity.version>5.3.0</serenity.version>
     <cucumber.version>7.34.2</cucumber.version>
     <junit.version>6.0.3</junit.version>
 </properties>
@@ -70,7 +70,7 @@ For Gradle, add to your `build.gradle`:
 
 ```groovy
 dependencies {
-    testImplementation "net.serenity-bdd:serenity-cucumber:5.2.4"
+    testImplementation "net.serenity-bdd:serenity-cucumber:5.3.0"
     testImplementation "io.cucumber:cucumber-junit-platform-engine:7.34.2"
     testImplementation "org.junit.platform:junit-platform-suite:6.0.3"
 }

docs/guide/annotation-requirements.md

@@ -8,7 +8,7 @@ sidebar_position: 7
 
 Serenity BDD organises test results into a _requirements hierarchy_, which provides the structure for the Living Documentation reports. By default, this hierarchy is derived from the package structure (for JUnit tests) or from the directory structure (for Cucumber feature files).
 
-Starting with Serenity 5.2.5, you can define the requirements hierarchy directly using **annotations** on your test classes. This provides a simple, explicit, and declarative way to organise your tests into a meaningful structure, without having to rely on package naming conventions.
+Starting with Serenity 5.3.0, you can define the requirements hierarchy directly using **annotations** on your test classes. This provides a simple, explicit, and declarative way to organise your tests into a meaningful structure, without having to rely on package naming conventions.
 
 ## The Requirements Hierarchy
 

docs/guide/maven.md

@@ -15,9 +15,9 @@ First, define the recommended versions in your properties section:
 
 ```xml
 <properties>
-    <serenity.version>5.2.2</serenity.version>
-    <junit5.version>6.0.1</junit5.version>
-    <cucumber.version>7.33.0</cucumber.version>
+    <serenity.version>5.3.0</serenity.version>
+    <junit5.version>6.0.3</junit5.version>
+    <cucumber.version>7.34.2</cucumber.version>
 </properties>
 ```
 

docs/junit5/junit5-tests.md

@@ -36,7 +36,7 @@ Add the following to your `pom.xml`:
 
 ```xml
 <properties>
-    <serenity.version>5.2.4</serenity.version>
+    <serenity.version>5.3.0</serenity.version>
     <junit.version>6.0.3</junit.version>
 </properties>
 
@@ -95,9 +95,9 @@ For Gradle, add to your `build.gradle`:
 
 ```groovy
 dependencies {
-    testImplementation "net.serenity-bdd:serenity-junit5:5.2.4"
-    testImplementation "net.serenity-bdd:serenity-screenplay:5.2.4"
-    testImplementation "net.serenity-bdd:serenity-screenplay-webdriver:5.2.4"
+    testImplementation "net.serenity-bdd:serenity-junit5:5.3.0"
+    testImplementation "net.serenity-bdd:serenity-screenplay:5.3.0"
+    testImplementation "net.serenity-bdd:serenity-screenplay-webdriver:5.3.0"
 
     testImplementation "org.junit.jupiter:junit-jupiter-api:6.0.3"
     testRuntimeOnly "org.junit.jupiter:junit-jupiter-engine:6.0.3"

docs/playwright/getting-started.md

@@ -24,7 +24,7 @@ Add the following dependencies to your `pom.xml`:
 
 ```xml
 <properties>
-    <serenity.version>5.2.4</serenity.version>
+    <serenity.version>5.3.0</serenity.version>
     <playwright.version>1.58.0</playwright.version>
     <junit.version>6.0.3</junit.version>
 </properties>

docs/playwright/screenplay-tutorial.md

@@ -22,7 +22,7 @@ Create a Maven project with these dependencies:
 
 ```xml
 <properties>
-    <serenity.version>5.2.4</serenity.version>
+    <serenity.version>5.3.0</serenity.version>
     <playwright.version>1.58.0</playwright.version>
 </properties>
 

docs/playwright/screenplay.md

@@ -38,7 +38,7 @@ Add these dependencies to your `pom.xml`:
 
 ```xml
 <properties>
-    <serenity.version>5.2.4</serenity.version>
+    <serenity.version>5.3.0</serenity.version>
     <playwright.version>1.58.0</playwright.version>
 </properties>
 

docs/playwright/tutorial-todomvc.md

@@ -34,7 +34,7 @@ First, create a Maven project with these dependencies in `pom.xml`:
         <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
         <maven.compiler.source>17</maven.compiler.source>
         <maven.compiler.target>17</maven.compiler.target>
-        <serenity.version>5.2.4</serenity.version>
+        <serenity.version>5.3.0</serenity.version>
         <playwright.version>1.58.0</playwright.version>
     </properties>
 

docs/reporting/living-documentation.md

@@ -399,7 +399,7 @@ In this case, the Serenity living documentation will treat the JUnit test cases
 
 #### Annotation-Based Hierarchy
 
-Starting with Serenity 5.2.5, you can also define the requirements hierarchy directly using the `@Epic`, `@Feature`, and `@Story` annotations on your test classes:
+Starting with Serenity 5.3.0, you can also define the requirements hierarchy directly using the `@Epic`, `@Feature`, and `@Story` annotations on your test classes:
 
 ```java
 @Feature("Managing Todos")

docs/tutorials/data-driven-testing.md

@@ -11,7 +11,7 @@ Data-driven testing allows you to run the same test logic with multiple sets of
 ## Prerequisites
 
 - Java 17 or higher
-- Serenity BDD 5.2.2 or higher
+- Serenity BDD 5.3.0 or higher
 - JUnit 5 6.0.1 or higher (for JUnit examples)
 - Cucumber 7.33.0 or higher (for Cucumber examples)