docs: add introduced label for payload-mode feature (#69)

dhrudevalia · web-flow · commit 579cdde81f4d · 2025-02-12T12:41:55.000Z
* docs: add introduced label for payload-mode feature

* docs: remove newline
diff --git a/modules/ROOT/pages/source/configuration.adoc b/modules/ROOT/pages/source/configuration.adoc
@@ -38,7 +38,7 @@ Default: `1000`
 | neo4j.payload-mode
 | Defines the structure of change messages. One of `COMPACT`, `EXTENDED`. `COMPACT` provides simpler messages but faces schema compatibility issues if property types change. `EXTENDED` includes type information to avoid such issues.
 
-Default: `EXTENDED`.
+Default: `EXTENDED`. label:new[Introduced in 5.1.5]
 |===
 
 == CDC Strategy Settings
diff --git a/modules/ROOT/pages/source/payload-mode.adoc b/modules/ROOT/pages/source/payload-mode.adoc
@@ -1,4 +1,5 @@
 = Kafka Source Connector: Payload Mode Configuration
+:page-role: new-5.1.5
 
 The Kafka Source Connector for Neo4j supports two payload modes to control the format of data serialized and published to Kafka topics: `EXTENDED` and `COMPACT`. This feature is configurable through the `neo4j.payload-mode` property, allowing users to select the preferred serialization format based on data requirements.
 

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,5 @@`
`1`	`1`	`= Kafka Source Connector: Payload Mode Configuration`
	`2`	`+:page-role: new-5.1.5`
`2`	`3`
`3`	`4`	The Kafka Source Connector for Neo4j supports two payload modes to control the format of data serialized and published to Kafka topics: `EXTENDED` and `COMPACT`. This feature is configurable through the `neo4j.payload-mode` property, allowing users to select the preferred serialization format based on data requirements.
`4`	`5`