From 0134a4b48bb0e868e7086b324c9f719cd166eca9 Mon Sep 17 00:00:00 2001
From: "A. Mahoney-Fernandes" <83057795+0xPlayerOne@users.noreply.github.com>
Date: Fri, 2 Oct 2026 13:09:07 -0400
Subject: [PATCH] fix: give the release artifact budgets several releases of
 headroom
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The 292_000/1_120_000 pair left 207/152 bytes of headroom over v1.40.0,
so v1.41.0's version pull request failed the unpacked budget with the
release tier blocking on it — the same CHANGELOG-growth wall the budget
comment already documents twice. Raise to 296_000/1_136_000 (~15
releases of changelog growth) per the comment's own guidance.
---
 scripts/performance-check.mjs | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/scripts/performance-check.mjs b/scripts/performance-check.mjs
index 9428a45..94dc55b 100644
--- a/scripts/performance-check.mjs
+++ b/scripts/performance-check.mjs
@@ -13,7 +13,10 @@ const root = resolve(fileURLToPath(new URL('..', import.meta.url)))
 // bytes on its own; 280_000 left under 400 bytes of headroom over v1.33.0 and
 // failed the release pull request itself, and 286_000 failed the same way two
 // releases later. Keep real headroom (several releases of CHANGELOG growth)
-// and raise it deliberately as the artifact grows.
+// and raise it deliberately as the artifact grows. The 292_000/1_120_000 pair
+// repeated that mistake — v1.41.0's version pull request measured 152 bytes
+// over the unpacked budget — so the 2026-10-02 bump leaves ~15 releases of
+// CHANGELOG growth instead of one.
 const budgets = {
   cliP95Ms: 250,
   runtimeP95Ms: 750,
@@ -21,8 +24,8 @@ const budgets = {
   ciChecksMs: 15_000,
   runtimeDependencies: 0,
   developmentDependencies: 4,
-  packedBytes: 292_000,
-  unpackedBytes: 1_120_000,
+  packedBytes: 296_000,
+  unpackedBytes: 1_136_000,
   packedFiles: 120,
 }