update Cargo.toml for release v2.6.0 (#1583)

* update Cargo.toml for release v2.6.0

* fix: reject numeric values for Timestamp fields in schema conflict detection

Arrow's JSON decoder with coerce_primitive(false) cannot decode a JSON number
(e.g., 1773595502.7462175) into a Timestamp field.
it expects a string like "2026-03-15T17:13:59Z"

this fixes the rejection when two log sources send same field -
one as timestamp other as float number

Author: nikhilsinhaparseable

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "parseable"
-version = "2.5.14"
+version = "2.6.0"
 authors = ["Parseable Team <hi@parseable.com>"]
 edition = "2024"
 rust-version = "1.88.0"
@@ -183,8 +183,8 @@ arrow = "57.1.0"
 temp-dir = "0.1.14"
 
 [package.metadata.parseable_ui]
-assets-url = "https://parseable-prism-build.s3.us-east-2.amazonaws.com/v2.5.14/build.zip"
-assets-sha1 = "7b3d1a6bea288585183cbc8233af4da91d768853"
+assets-url = "https://parseable-prism-build.s3.us-east-2.amazonaws.com/v2.6.0/build.zip"
+assets-sha1 = "877e8f6f6b80bdd57c3c8a076464a0a90e29974c"
 
 [features]
 debug = []

Cargo.toml

@@ -434,7 +434,9 @@ fn value_compatible_with_type(
                         || chrono::NaiveDateTime::parse_from_str(s, "%Y-%m-%d %H:%M:%S%.f").is_ok()
                         || chrono::NaiveDateTime::parse_from_str(s, "%Y-%m-%d %H:%M:%S").is_ok()
                 }
-                Value::Number(_) => true,
+                // Arrow JSON decoder with coerce_primitive(false) cannot decode
+                // a JSON number into a Timestamp field — it expects a string.
+                Value::Number(_) => false,
                 _ => false,
             }
         }