From 580fcdde4ce8bc7dd42ccbcabe4062de9a86ce7d Mon Sep 17 00:00:00 2001
From: "pre-commit-ci[bot]"
 <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Date: Tue, 22 Jul 2025 10:51:47 +0000
Subject: [PATCH] =?UTF-8?q?fix(pre=5Fcommit):=20=F0=9F=8E=A8=20auto=20form?=
 =?UTF-8?q?at=20pre-commit=20hooks?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/changelog.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/changelog.md b/docs/changelog.md
index b1ba1f41..67231d24 100644
--- a/docs/changelog.md
+++ b/docs/changelog.md
@@ -4,7 +4,7 @@
 
 - Fix ([1894](https://github.com/roboflow/supervision/pull/1894)): Fixed error in `sv.MeanAveragePrecision` where the area used for size-specific evaluation (small / medium / large) was always zero unless explicitly provided in `sv.Detections.data`.
 
-- Fix ([1895](https://github.com/roboflow/supervision/pull/1895)): Fixed `ID=0` bug in `sv.MeanAveragePrecision` where objects were getting `0.0` mAP despite perfect IoU matches due to a bug in annotation ID assignment. 
+- Fix ([1895](https://github.com/roboflow/supervision/pull/1895)): Fixed `ID=0` bug in `sv.MeanAveragePrecision` where objects were getting `0.0` mAP despite perfect IoU matches due to a bug in annotation ID assignment.
 
 -  Fix ([1898](https://github.com/roboflow/supervision/pull/1898)): Fixed issue where `sv.MeanAveragePrecision` could return negative values when certain object size categories have no data.