fix(server): prefer write-clause type in extract_crud_info, bump to 1.4.3 (#121)

For Match + Insert/Put queries, extract_crud_info() was reporting the
first matched entity as type_name instead of the actual write target.
Separate match-clause type info into fallback variables so the
Insert/Put statement always takes priority.

Also refactor validation.rs match arms to use idiomatic match guards.

Author: ds1sqe

CHANGELOG.md

@@ -4,6 +4,16 @@ All notable changes to TypeBridge will be documented in this file.
 
 ## [Unreleased]
 
+## [1.4.3] - 2026-04-05
+
+### Bug Fixes
+
+##### Rust Server — `type-bridge-server`
+- **fix**: `extract_crud_info()` now reports the write-target type for Match + Insert/Put queries (#121)
+
+##### Rust Core — `type-bridge-core-lib`
+- **refactor**: use idiomatic match guards in validation.rs
+
 ## [1.4.2] - 2026-03-04
 
 ##### Rust Server — `type-bridge-server`

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "type-bridge"
-version = "1.4.2"
+version = "1.4.3"
 description = "A modern, Pythonic ORM for TypeDB with an Attribute-based API"
 readme = "README.md"
 requires-python = ">=3.13"
@@ -29,7 +29,7 @@ dependencies = [
     "lark>=1.1.9",
     "jinja2>=3.1.0",
     "typer>=0.15.0",
-    "type-bridge-core>=1.4.2",
+    "type-bridge-core>=1.4.3",
 ]
 
 [project.urls]