visiq 0.1.1-x86_64-linux → 0.1.2-x86_64-linux
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/lib/visiq.rb +21 -1
- data/vendor/libvisiq_core.so +0 -0
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 7dbb31a8e823edb4aef346185fbb5a0b5158216679bc7adfb51c3b42b9a7860e
|
|
4
|
+
data.tar.gz: 74e1c290d372e45c56ce266e832775f9851f6929cd92733614ca04aa9ede4361
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 63282971a7c52551376efb0cf336c161ec89c7558e53880ec42e025a3ca5fc3d71854b67381d6cd35d14f9c42621990373170fc5f7a852423be2ff7b64b1bc5d
|
|
7
|
+
data.tar.gz: e362ca021ad313422efaf0bc09357de343928ab827c0b21ae308aaf2ac60d2b166e187e415aa00fc6632bbd092946fd249b3c18a3535204e160691732a69fa47
|
data/lib/visiq.rb
CHANGED
|
@@ -23,7 +23,27 @@ require "json"
|
|
|
23
23
|
require "rbconfig"
|
|
24
24
|
|
|
25
25
|
module Visiq
|
|
26
|
-
|
|
26
|
+
# 0.1.1 -> 0.1.2 republishes the SAME Ruby source against a REBUILT core.
|
|
27
|
+
#
|
|
28
|
+
# WHY A BUMP IS THE FIX. `sdk-published-freshness.yml` replays the current oracle
|
|
29
|
+
# corpus through each PUBLISHED artifact's own bundled core. The gem at 0.1.1
|
|
30
|
+
# reproduces 133 of 135 vectors: it predates the source-3 named-detector work, so
|
|
31
|
+
# its core never fills `write.data_categories`, a customer rule of the form
|
|
32
|
+
# `mask { "pii" in input.normalized.write.data_categories }` abstains, and the
|
|
33
|
+
# no-coverage floor denies the write instead of masking it. Fail-closed, but wrong
|
|
34
|
+
# — a customer who asked for redaction gets a hard denial (D-WRITE-DENY).
|
|
35
|
+
#
|
|
36
|
+
# The Ruby source needs no change; only a REBUILD does, and `rubygems-publish.yml`
|
|
37
|
+
# compiles the C-ABI core from current source on every publish. Its version guard
|
|
38
|
+
# reads the gemspec (which reads this constant), so an unchanged version is a
|
|
39
|
+
# whole-pipeline no-op — which is exactly why the lane has been red since
|
|
40
|
+
# 2026-08-01 with a landed fix that could never ship. Bumping is the trigger.
|
|
41
|
+
#
|
|
42
|
+
# NOT COUPLED TO THE PYTHON HOLD. visiq-core-rs stays pinned at 0.2.4 for the
|
|
43
|
+
# Semantic-Kernel adapter defect (see its Cargo.toml). That hold gates the PyPI
|
|
44
|
+
# wheel, which ships the core's own version; Ruby and Java version independently
|
|
45
|
+
# and are not implicated. Bumping here does not resume the Python release.
|
|
46
|
+
VERSION = "0.1.2"
|
|
27
47
|
|
|
28
48
|
# Low-level binding to the compiled core over the C-ABI seam.
|
|
29
49
|
module Core
|
data/vendor/libvisiq_core.so
CHANGED
|
Binary file
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: visiq
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.1.
|
|
4
|
+
version: 0.1.2
|
|
5
5
|
platform: x86_64-linux
|
|
6
6
|
authors:
|
|
7
7
|
- VisIQ Labs Team
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2026-
|
|
11
|
+
date: 2026-08-11 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: fiddle
|