From de8f489812057625058ad06c1247bc118167c790 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Tue, 30 Jun 2026 18:47:32 +0000
Subject: [PATCH] Add change note for instance-attribute type-tracking
 performance fix

---
 .../2026-06-30-instance-attribute-typetracking-performance.md | 4 ++++
 1 file changed, 4 insertions(+)
 create mode 100644 python/ql/lib/change-notes/2026-06-30-instance-attribute-typetracking-performance.md

diff --git a/python/ql/lib/change-notes/2026-06-30-instance-attribute-typetracking-performance.md b/python/ql/lib/change-notes/2026-06-30-instance-attribute-typetracking-performance.md
new file mode 100644
index 00000000000..53532f6e65c
--- /dev/null
+++ b/python/ql/lib/change-notes/2026-06-30-instance-attribute-typetracking-performance.md
@@ -0,0 +1,4 @@
+---
+category: minorAnalysis
+---
+* Type tracking of values stored in instance attributes and read from outside the class (for example `instance.attr` where the value was assigned to `self.attr` in a method) no longer relies on a dedicated instance type-tracker. This avoids a structural mutual recursion that could cause catastrophic query slowdowns on some OOP-heavy code bases. Such reads are now resolved using local flow from the constructor call, which is slightly less precise for instances that flow across a call or return before being read.