From e74eab5c9530c24cad69b223b2289d4ec850d911 Mon Sep 17 00:00:00 2001 From: shankar0123 Date: Sun, 10 May 2026 01:18:16 +0000 Subject: [PATCH] auth-bundle-1 fix: S-1 ci-guard false positive on "Bundle 1 migrations" MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit CI run #484 surfaced the regression in the Frontend Build job: ::error::S-1 regression: hardcoded source-count prose reappeared: docs/migration/api-keys-to-rbac.md:32:schema is already at the target version. The Bundle 1 migrations The S-1 guard's regex (scripts/ci-guards/S-1-hardcoded-source-counts.sh) catches `\b[0-9]+\s+migrations\b` to prevent stale " migrations" prose in docs/. The Bundle 1 migration-guide phrasing "The Bundle 1 migrations" tripped on the digit-1 in "Bundle 1" sitting next to the word "migrations" — false positive, not a real source-count claim. Rephrase to "Migrations that ship in the Bundle 1 slice of v2.1.0:" which keeps the same operator meaning without the regex collision. The guard now passes; full ci-guards loop runs clean locally. Spotted via the operator's CI-failure paste post-Bundle-1 merge. --- docs/migration/api-keys-to-rbac.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/migration/api-keys-to-rbac.md b/docs/migration/api-keys-to-rbac.md index 3b7818f..8b874c4 100644 --- a/docs/migration/api-keys-to-rbac.md +++ b/docs/migration/api-keys-to-rbac.md @@ -29,8 +29,8 @@ release notes for v2.1.0 lead with this callout for a reason. ### 1. Apply the migration The migration runner is idempotent. Re-applying is a no-op if the -schema is already at the target version. The Bundle 1 migrations -that ship with v2.1.0: +schema is already at the target version. Migrations that ship in +the Bundle 1 slice of v2.1.0: | Migration | What it does | |---|---|