docs: update release notes for v0.10.2 with bug fixes and changelog (#181)

Release v0.10.2 docs updated

---------

Co-authored-by: Danny Meijer <10511979+dannymeijer@users.noreply.github.com>

Author: dannymeijer

docs/releases/0.10.md

@@ -10,6 +10,7 @@ Big shout out to all contributors and a heartfelt welcome to our new contributor
 
 * @nogitting made their first contribution in https://github.com/Nike-Inc/koheesio/pull/154
 * @zarembat made their first contribution in https://github.com/Nike-Inc/koheesio/pull/163
+* @brunodd made their first contribution in https://github.com/Nike-Inc/koheesio/pull/180
 
 ## Migrating from v0.9
 
@@ -23,6 +24,43 @@ For users currently using v0.9, consider the following:
 
 * `JDBCReader`, `HanaReader`, and `TeradataReader` classes have been updated to use `params` over `options` for improved consistency and maintainability. The `options` field has been renamed to `params`, and an alias `options` has been added for backwards compatibility. These changes provide a more consistent API across different reader classes and improve code readability. Note that `dbtable` and `query` validation now occurs upon *initialization* rather than at *runtime*, requiring either `dbtable` or `query` to be submitted to use JDBC based classes.
 
+## Release 0.10.2
+
+**v0.10.2** - *2025-04-02*
+
+* **Full Changelog**:
+    https://github.com/Nike-Inc/koheesio/compare/koheesio-v0.10.1...koheesio-v0.10.2
+
+!!! bug "bugfix - PR [#177](https://github.com/Nike-Inc/koheesio/pull/177), related issue #178"
+    #### *Tableau*: Hyper process would fail on DBFS
+
+    Fixed a bug causing the Hyper process to fail when DBFS was used as a target destination for the HyperAPI process. 
+
+    Users reported that despite the fact that the process worked as expected on DBR 13.3, it was failing on 15.4.
+    Hyper will now be generated using local filesystem in all cases and then it will be moved to the location that user 
+    specified in the `path` parameter during class init, it could be DBFS or other compatible file system.
+
+    <small> by @maxim-mityutko</small>
+
+!!! bug "bugfix - PR [#179](https://github.com/Nike-Inc/koheesio/pull/179)"
+    #### *Delta > Writer*: Fixed checking merge builder type in DeltaTableWriter when using connect
+
+    * The `merge_builder` parameter in `DeltaTableWriter` was not properly validating the type of the merge builder when using Spark Connect.
+    * The validation logic was expecting a `list` or a `delta.tables.DeltaMergeBuilder` instance, but it failed to recognize the `delta.connect.tables.DeltaMergeBuilder` instance.
+    * 4 dedicated test cases have been added to test the merge builder
+
+    <small> by @zarembat</small>
+
+!!! bug "bugfix - PR [#180](https://github.com/Nike-Inc/koheesio/pull/180)"
+    #### *Snowflake > Spark*: Ensure matched inserts sync to Snowflake
+
+    * Ensure a new INSERT is synchronized to Snowflake, even when a match is already found.
+    
+    When a Delta table is VACUUMed before a sync to Snowflake was triggered, a updated record will be considered as an "INSERT" record. 
+    However the target table might already contain this record. This fix ensures that this record is still updated as would be desired.
+
+    <small> by @brunodd</small>
+
 ## Release 0.10.1
 
 **v0.10.1** - *2025-03-11*