[DOP-27545] fix changelog

Author: Anna Mikhaylova

mddocs/changelog.md

@@ -1,10 +1,10 @@
 # Changelog { #changelog }
 
-- [0.2.5 [UNRELEASED] (2025-09-30)][DRAFT]
-- [0.2.4 (2026-03-05)][0.3.2]
-- [0.2.4 (2026-01-15)][0.3.1]
-- [0.2.4 (2025-12-18)][0.3.0]
-- [0.2.4 (2025-10-10)][0.2.5]
+- [0.3.3 [UNRELEASED] (2025-09-30)][DRAFT]
+- [0.3.2 (2026-03-05)][0.3.2]
+- [0.3.1 (2026-01-15)][0.3.1]
+- [0.3.0 (2025-12-18)][0.3.0]
+- [0.2.5 (2025-10-10)][0.2.5]
 - [0.2.4 (2025-07-09)][0.2.4]
 - [0.2.3 (2025-04-11)][0.2.3]
 - [0.2.2 (2025-04-11)][0.2.2]

mddocs/changelog/0.1.2.md

@@ -2,11 +2,11 @@
 
 ## Features
 
-- Rename `syncmaster.backend.main` module to `syncmaster.backend`. It now also accepts the same args as `uvicorn`. ([#35](https://github.com/MobileTeleSystems/syncmaster/issues/35))
-- Add `syncmaster.db.migrations` module to run `alembic` with proper config. ([#35](https://github.com/MobileTeleSystems/syncmaster/issues/35))
-- Change backend and worker images to use entrypoint. ([#35](https://github.com/MobileTeleSystems/syncmaster/issues/35))
+- Rename `syncmaster.backend.main` module to `syncmaster.backend`. It now also accepts the same args as `uvicorn`. [#35](https://github.com/MobileTeleSystems/syncmaster/issues/35)
+- Add `syncmaster.db.migrations` module to run `alembic` with proper config. [#35](https://github.com/MobileTeleSystems/syncmaster/issues/35)
+- Change backend and worker images to use entrypoint. [#35](https://github.com/MobileTeleSystems/syncmaster/issues/35)
 
 ## Improvements
 
-- Run database migrations in the entrypoint of backend image, before starting the backend server. ([#35](https://github.com/MobileTeleSystems/syncmaster/issues/35))
-- Add healthchecks to example `docker-compose.yml`. ([#35](https://github.com/MobileTeleSystems/syncmaster/issues/35))
+- Run database migrations in the entrypoint of backend image, before starting the backend server. [#35](https://github.com/MobileTeleSystems/syncmaster/issues/35)
+- Add healthchecks to example `docker-compose.yml`. [#35](https://github.com/MobileTeleSystems/syncmaster/issues/35)

mddocs/changelog/0.1.5.md

@@ -3,15 +3,15 @@
 ## Breaking Changes
 
 - Pass current `Run` to `CREATE_SPARK_SESSION_FUNCTION`. This allows using run/transfer/group information for Spark session options,
-  like `appName` or custom ones. ([#38](https://github.com/MobileTeleSystems/syncmaster/issues/38))
+  like `appName` or custom ones. [#38](https://github.com/MobileTeleSystems/syncmaster/issues/38)
 
 ## Improvements
 
-- Reduce backend image size ([#44](https://github.com/MobileTeleSystems/syncmaster/issues/44))
+- Reduce backend image size [#44](https://github.com/MobileTeleSystems/syncmaster/issues/44)
 
 ## Bug Fixes
 
-- Fix 500 error in case of `PATCH v1/connections/:id` request with passed `auth_data.password` field value ([#39](https://github.com/MobileTeleSystems/syncmaster/issues/39))
-- Do not use `asyncio.gather` with SQLAlchemy requests ([#40](https://github.com/MobileTeleSystems/syncmaster/issues/40))
-- Fix 500 error while creating HDFS connection ([#41](https://github.com/MobileTeleSystems/syncmaster/issues/41))
+- Fix 500 error in case of `PATCH v1/connections/:id` request with passed `auth_data.password` field value [#39](https://github.com/MobileTeleSystems/syncmaster/issues/39)
+- Do not use `asyncio.gather` with SQLAlchemy requests [#40](https://github.com/MobileTeleSystems/syncmaster/issues/40)
+- Fix 500 error while creating HDFS connection [#41](https://github.com/MobileTeleSystems/syncmaster/issues/41)
 - Fix missing `options` field from Transfer params with `hdfs` and `s3` type

mddocs/changelog/0.2.0.md

@@ -13,15 +13,15 @@ Huge thanks to [Dmitry Pedchenko](https://github.com/dmitry-pedchenko), [Maxim L
 
 ## Breaking Changes
 
-- Implement a single error handling format to improve consistency ([#95](https://github.com/MobileTeleSystems/syncmaster/issues/95))
-- Change response format for `GET /v1/groups` - add **current user role** for each group ([#97](https://github.com/MobileTeleSystems/syncmaster/issues/97))
-- Change response format for `GET /v1/groups/:id` - add **current user role** for group ([#109](https://github.com/MobileTeleSystems/syncmaster/issues/109))
-- Now migrations are executed in a dedicated one-off container, instead of being run as a part of `backend` container. ([#163](https://github.com/MobileTeleSystems/syncmaster/issues/163))
-- Delete **transfers**, **queues** and **groups** records instead of marking them as deleted ([#168](https://github.com/MobileTeleSystems/syncmaster/issues/168))
-- Move the `type` field from nested `connection_data` field to the root level of the `Connection` response. ([#169](https://github.com/MobileTeleSystems/syncmaster/issues/169))
-- Decouple `auth_data.type` from the connection type (e.g. `postgres`) and link it to the authentication type (e.g. `basic`). ([#169](https://github.com/MobileTeleSystems/syncmaster/issues/169))
-- Add deletion of **connections** records instead of marking them as deleted ([#170](https://github.com/MobileTeleSystems/syncmaster/issues/170))
-- Use PUT instead of PATCH for `Connection` and `Transfer` models ([#215](https://github.com/MobileTeleSystems/syncmaster/issues/215))
+- Implement a single error handling format to improve consistency [#95](https://github.com/MobileTeleSystems/syncmaster/issues/95)
+- Change response format for `GET /v1/groups` - add **current user role** for each group [#97](https://github.com/MobileTeleSystems/syncmaster/issues/97)
+- Change response format for `GET /v1/groups/:id` - add **current user role** for group [#109](https://github.com/MobileTeleSystems/syncmaster/issues/109)
+- Now migrations are executed in a dedicated one-off container, instead of being run as a part of `backend` container. [#163](https://github.com/MobileTeleSystems/syncmaster/issues/163)
+- Delete **transfers**, **queues** and **groups** records instead of marking them as deleted [#168](https://github.com/MobileTeleSystems/syncmaster/issues/168)
+- Move the `type` field from nested `connection_data` field to the root level of the `Connection` response. [#169](https://github.com/MobileTeleSystems/syncmaster/issues/169)
+- Decouple `auth_data.type` from the connection type (e.g. `postgres`) and link it to the authentication type (e.g. `basic`). [#169](https://github.com/MobileTeleSystems/syncmaster/issues/169)
+- Add deletion of **connections** records instead of marking them as deleted [#170](https://github.com/MobileTeleSystems/syncmaster/issues/170)
+- Use PUT instead of PATCH for `Connection` and `Transfer` models [#215](https://github.com/MobileTeleSystems/syncmaster/issues/215)
 - Return new connection and transfer object in `POST /v1/transfer/copy` and `POST /v1/connection/copy` endpoints.
 - Change response status from 200 to 204 for all `DELETE` endpoints.
 

mddocs/changelog/0.3.0.md

@@ -52,7 +52,7 @@ auth:
 
 ## Features
 
-- Added Iceberg support (([#282](https://github.com/MobileTeleSystems/syncmaster/issues/282)), ([#284](https://github.com/MobileTeleSystems/syncmaster/issues/284)), ([#294](https://github.com/MobileTeleSystems/syncmaster/issues/294)), ([#297](https://github.com/MobileTeleSystems/syncmaster/issues/297))).
+- Added Iceberg support ([#282](https://github.com/MobileTeleSystems/syncmaster/issues/282), [#284](https://github.com/MobileTeleSystems/syncmaster/issues/284), [#294](https://github.com/MobileTeleSystems/syncmaster/issues/294), [#297](https://github.com/MobileTeleSystems/syncmaster/issues/297)).
 
   Iceberg connection currently supports only Iceberg REST Catalog with S3 warehouse.
 

mddocs/changelog/0.3.2.md

@@ -2,4 +2,4 @@
 
 ## Features
 
-Implement SQL transformations for transfer (([#327](https://github.com/MobileTeleSystems/syncmaster/issues/327)), ([#330](https://github.com/MobileTeleSystems/syncmaster/issues/255)))
+Implement SQL transformations for transfer ([#327](https://github.com/MobileTeleSystems/syncmaster/issues/327), [#330](https://github.com/MobileTeleSystems/syncmaster/issues/255))

mddocs/changelog/index.md

@@ -1,10 +1,10 @@
 # Changelog { #changelog }
 
-* [0.2.5 [UNRELEASED] (2025-09-30)][DRAFT]
-* [0.2.4 (2026-03-05)][0.3.2]
-* [0.2.4 (2026-01-15)][0.3.1]
-* [0.2.4 (2025-12-18)][0.3.0]
-* [0.2.4 (2025-10-10)][0.2.5]
+* [0.3.3 [UNRELEASED]][DRAFT]
+* [0.3.2 (2026-03-05)][0.3.2]
+* [0.3.1 (2026-01-15)][0.3.1]
+* [0.3.0 (2025-12-18)][0.3.0]
+* [0.2.5 (2025-10-10)][0.2.5]
 * [0.2.4 (2025-07-09)][0.2.4]
 * [0.2.3 (2025-04-11)][0.2.3]
 * [0.2.2 (2025-04-11)][0.2.2]

mddocs/reference/worker/create_spark_session.md

@@ -10,27 +10,27 @@ It is possible to alter default [Spark Session configuration](https://spark.apac
 
 ```yaml
 worker:
-        spark_session_default_config:
-            spark.master: local
-            spark.driver.host: 127.0.0.1
-            spark.driver.bindAddress: 0.0.0.0
-            spark.sql.pyspark.jvmStacktrace.enabled: true
-            spark.ui.enabled: false
+    spark_session_default_config:
+        spark.master: local
+        spark.driver.host: 127.0.0.1
+        spark.driver.bindAddress: 0.0.0.0
+        spark.sql.pyspark.jvmStacktrace.enabled: true
+        spark.ui.enabled: false
 ```
 
 For example, to use SyncMaster on Spark-on-K8s, you can use worker image for Spark executor containers:
 
 ```yaml
-    worker:
-        spark_session_default_config:
-            spark.master: k8s://https://kubernetes.default.svc
-            spark.driver.host: service-for-spark-driver
-            spark.driver.bindAddress: 0.0.0.0
-            spark.driver.port: 10000
-            spark.blockManager.port: 10001
-            spark.kubernetes.authenticate.driver.serviceAccountName: spark
-            spark.sql.pyspark.jvmStacktrace.enabled: true
-            spark.kubernetes.container.image: mtsrus/syncmaster-worker:{TAG}
+worker:
+    spark_session_default_config:
+        spark.master: k8s://https://kubernetes.default.svc
+        spark.driver.host: service-for-spark-driver
+        spark.driver.bindAddress: 0.0.0.0
+        spark.driver.port: 10000
+        spark.blockManager.port: 10001
+        spark.kubernetes.authenticate.driver.serviceAccountName: spark
+        spark.sql.pyspark.jvmStacktrace.enabled: true
+        spark.kubernetes.container.image: mtsrus/syncmaster-worker:{TAG}
 ```
 
 !!! note
@@ -42,26 +42,26 @@ For example, to use SyncMaster on Spark-on-K8s, you can use worker image for Spa
 It is also possible to use custom function which returns ``SparkSession`` object:
 
 ```yaml
-    worker:
-        create_spark_session_function: my_worker.spark.create_custom_spark_session
+worker:
+    create_spark_session_function: my_worker.spark.create_custom_spark_session
 ```
 
 Here is a function example:
 
-```python
-    from syncmaster.db.models import Run
-    from syncmaster.dto.connections import ConnectionDTO
-    from syncmaster.worker.settings import WorkerSettings
-    from pyspark.sql import SparkSession
+```python title="my_workers/spark.py"
+from syncmaster.db.models import Run
+from syncmaster.dto.connections import ConnectionDTO
+from syncmaster.worker.settings import WorkerSettings
+from pyspark.sql import SparkSession
 
-    def create_custom_spark_session(
-        run: Run,
-        source: ConnectionDTO,
-        target: ConnectionDTO,
-        settings: WorkerSettings,
-    ) -> SparkSession:
-        # any custom code returning SparkSession object
-        return SparkSession.builde.config(...).getOrCreate()
+def create_custom_spark_session(
+    run: Run,
+    source: ConnectionDTO,
+    target: ConnectionDTO,
+    settings: WorkerSettings,
+) -> SparkSession:
+# any custom code returning SparkSession object
+return SparkSession.builde.config(...).getOrCreate()
 ```
 
 Module with custom function should be placed into the same Docker image or Python virtual environment used by SyncMaster worker.