gsadmin/certctl
1
0
Fork 0
mirror of https://github.com/shankar0123/certctl.git synced 2026-06-07 14:21:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

auth-bundle-1 fix: S-1 ci-guard false positive on "Bundle 1 migrations"

Browse Source 
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 "<N> 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.
This commit is contained in:
shankar0123
2026-05-10 01:18:16 +00:00
parent 22c4971012
commit 51f55c5fc9
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/migration/api-keys-to-rbac.md
+2 -2
View File
@@ -29,8 +29,8 @@ release notes for v2.1.0 lead with this callout for a reason.
### 1. Apply the migration ### 1. Apply the migration
The migration runner is idempotent. Re-applying is a no-op if the The migration runner is idempotent. Re-applying is a no-op if the
schema is already at the target version. The Bundle 1 migrations schema is already at the target version. Migrations that ship in
that ship with v2.1.0: the Bundle 1 slice of v2.1.0:
| Migration | What it does | | Migration | What it does |
|---|---| |---|---|