IRIS-NG-v1.1.1: retarget from the never-tagged v1.1.0, document the advisories
v1.1.0 was staged on main but never tagged, so every reference to it as the
release a change shipped in was wrong. Retargeted across AI-Features,
Dependency-Policy, IOC-Correlation, Changelog and Kubernetes.
Changelog gains the two UI dependency advisories cleared in v1.1.1
(brace-expansion, socket.io-parser) and links the release.
Kubernetes: chart 0.5.1, appVersion IRIS-NG-v1.1.1, pull commands updated.
Correlation scoring rewrite, AI troubleshooting, dependency policy
Changelog: adds IRIS-NG-v1.0.2, and IRIS-NG-v1.1.0 marked pending release.
Records that IRIS-NG-v1.0.3 was never released — the version was staged on
main but no tag, release or images were produced, so nothing shipped under
that number and its changes land in v1.1.0.
IOC Correlation: the scoring sections described algorithms that no longer
match the code, and the how-it-works step repeated a misconception the
control's own label encouraged — that "Min shared IOCs" counts cases an
indicator appears in. It counts indicators a case PAIR must share. Rewritten
to state that plainly, with the consequence spelled out: an indicator's fate
is decided by its neighbours, not by itself, so two indicators each present
in exactly two cases can be treated differently.
Decay and confidence rewritten to match what ships in v1.1.0 — tags scale
the half-life rather than the score, age comes from the most recent sighting,
TLP no longer participates, and confidence weighs rarity and credibility
rather than counting indicators. Flags that figures will read lower than
earlier releases, which is a real change analysts will notice.
AI Features: per-surface timeout table replacing the stale 60-90s note, plus
a Troubleshooting section covering the three failures that are hard to tell
apart — an unrecognised model identifier, a model declining security content,
and a timeout — since before v1.1.0 all three displayed the same JSON parse
error.
New Dependency Policy page: why PostgreSQL, jQuery, Node, marshmallow and the
report generator stack are held back, and how to verify a dependency change.
A green build is not evidence a Python upgrade worked; the pkg_resources case
is the reference example, where the image builds cleanly and the application
dies at startup.