fix(ci): resolve workspace-inherited version in publish-crates

grep '^version' returned the literal 'true' for manifests using
version.workspace = true, defeating the already-published pre-check.
Use cargo metadata to expand the real workspace version.

Author: AlexMikhalev

.github/workflows/publish-crates.yml

@@ -38,7 +38,16 @@ jobs:
               echo "Missing manifest for $crate at $manifest" >&2
               exit 1
             fi
-            version=$(grep -m1 '^version' "$manifest" | sed 's/.*"\(.*\)".*/\1/')
+            # Resolve the real version via cargo metadata so that
+            # `version.workspace = true` is expanded to the workspace value.
+            # (A naive `grep '^version'` yields the literal "true".)
+            version=$(cargo metadata --no-deps --format-version=1 \
+              | jq -r --arg manifest "$manifest" \
+                '.packages[] | select(.manifest_path | endswith($manifest)) | .version')
+            if [ -z "$version" ]; then
+              echo "ERROR: could not resolve version for $crate from $manifest" >&2
+              exit 1
+            fi
             # Check crates.io with auth to avoid rate limits
             if curl -fsS -H "Authorization: ${CARGO_REGISTRY_TOKEN}" "https://crates.io/api/v1/crates/$crate/$version" >/dev/null 2>&1; then
               echo "$crate $version already exists on crates.io; skipping"