oh-my-customcode 1.1.34 → 1.1.35
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/cli/index.js
CHANGED
package/dist/index.js
CHANGED
package/package.json
CHANGED
|
@@ -77,16 +77,21 @@ Wiki verification is also enforced by CI (`.github/workflows/wiki-sync.yml`).
|
|
|
77
77
|
```
|
|
78
78
|
-->
|
|
79
79
|
|
|
80
|
-
### Release Commit Staging Hygiene (빌드 산출물
|
|
80
|
+
### Release Commit Staging Hygiene (빌드 산출물 오염/누락 방지)
|
|
81
81
|
|
|
82
|
-
릴리즈 커밋(및 `bun run build`를 수행한 모든 커밋) 직전,
|
|
82
|
+
릴리즈 커밋(및 `bun run build`를 수행한 모든 커밋) 직전, 스테이징 검증은 **양방향**이다 — (a) gitignored 빌드 산출물(`dist/` 등)이 **혼입**되지 않았는가, (b) 빌드가 갱신한 **tracked** 산출물(`.omcustom.lock.json` 등)이 **누락**되지 않았는가. 두 방향은 서로 다른 경로(gitignored vs tracked)를 대상으로 하므로, 한쪽만 확인하면 반대 방향 결함이 통과한다 — .gitignore 존재/부재 확인만으로는 부족하다.
|
|
83
|
+
|
|
84
|
+
**(a) 혼입 방지**: `git diff --cached --name-only`로 **스테이징 목록을 실측**하여 `dist/` 등 빌드 산출물이 포함되지 않았는지 확인한다. gitignored 경로라도 `git add -f` 또는 광범위 `git add` 조합으로 스테이징될 수 있다. 발견 시 `git reset dist/`로 제외한 뒤 커밋한다. 이는 v1.1.12의 `dist/` untrack 조치에 대한 **회귀 방지 게이트**다.
|
|
85
|
+
|
|
86
|
+
**(b) 누락 방지**: `bun run build` 실행 후 `git status --short`에 **tracked 변경(`^ M`)이 남아 있으면 스테이징 누락**이다. 커밋 직전 tracked 변경이 0인지 확인한다.
|
|
83
87
|
|
|
84
88
|
| Anti-pattern | Required |
|
|
85
89
|
|--------------|----------|
|
|
86
90
|
| 빌드 후 광범위 `git add`로 커밋 → gitignored `dist/` force-add 위험 | 커밋 직전 `git diff --cached --name-only` 실측으로 빌드 산출물 부재 확인 |
|
|
87
91
|
| .gitignore에 있으니 안전하다고 가정 | force-add 경로는 .gitignore를 우회하므로 실측 필요 |
|
|
92
|
+
| `dist/` 미포함만 확인하고 커밋 → 빌드가 갱신한 tracked 산출물 누락 | `git status --short`로 tracked 변경 잔존 0 확인 |
|
|
88
93
|
|
|
89
|
-
Origin: #1512 (v1.1.28 커밋 staging에 dist/ 2파일 포함, 커밋 전 실측으로 정정; v1.1.12 dist/ untrack 회귀 방지). Cross-ref: R020 (완료 검증 — "실행됨 ≠ 성공").
|
|
94
|
+
Origin: #1512 (v1.1.28 커밋 staging에 dist/ 2파일 포함, 커밋 전 실측으로 정정; v1.1.12 dist/ untrack 회귀 방지); #1531 (`.omcustom.lock.json`이 v1.1.29 이후 4개 릴리즈 연속 누락 — 혼입 방지 단방향 조항의 반대편 공백). Cross-ref: R020 (완료 검증 — "실행됨 ≠ 성공").
|
|
90
95
|
|
|
91
96
|
### Count Sync — Exhaustive Grep, Not File Enumeration
|
|
92
97
|
|
|
@@ -307,9 +307,13 @@ steps:
|
|
|
307
307
|
# Edit ONLY the .version field — do NOT overwrite templates/manifest.json wholesale (e.g. a source-hash path→hash map).
|
|
308
308
|
# Recover a corrupted manifest: git show HEAD:templates/manifest.json | jq '.version="<NEW>"' > templates/manifest.json (#1423/#1154).
|
|
309
309
|
b. templates/manifest.json: jq '.version = "<NEW>"' templates/manifest.json > templates/manifest.json.tmp && mv templates/manifest.json.tmp templates/manifest.json
|
|
310
|
-
c.
|
|
311
|
-
|
|
312
|
-
|
|
310
|
+
c. bun run build — run standalone (NO pipe), read exit code directly ($? after a pipe is the last command's, R005/#1492).
|
|
311
|
+
This regenerates .omcustom.lock.json (generatorVersion/templateVersion) to <NEW> via scripts/sync-source-lockfile.ts.
|
|
312
|
+
d. git status --short — enumerate ALL tracked drift (`^ M`) the build produced; stage EVERY one (esp. .omcustom.lock.json) before commit.
|
|
313
|
+
(#1531 — .omcustom.lock.json missed staging across 4 consecutive releases after v1.1.29; root cause was no build step between version bump and commit.)
|
|
314
|
+
e. mgr-gitnerd commit: "chore(release): bump to v<NEW>" — MUST include the drift from step d
|
|
315
|
+
f. mgr-gitnerd push develop
|
|
316
|
+
g. mandatory verification (with existence guard for partial-update safety):
|
|
313
317
|
[ -f scripts/verify-version-sync.sh ] && bash scripts/verify-version-sync.sh || echo "::warning::verify-version-sync.sh not found, version sync verification skipped"
|
|
314
318
|
(verify-version-sync.sh 가 exit 1 시 release 단계 halt)
|
|
315
319
|
|
|
@@ -325,12 +329,15 @@ steps:
|
|
|
325
329
|
3. Adapt release mechanism to project (determines how steps 3-5 execute):
|
|
326
330
|
- npm project with auto-tag.yml (this repo — release/v* PR pattern):
|
|
327
331
|
a. mgr-gitnerd creates release/v{NEW} branch from develop with the version-bump commit
|
|
328
|
-
b. mgr-gitnerd creates PR: gh pr create --base develop --head release/v{NEW} --title "chore(release): bump to v{NEW}"
|
|
332
|
+
b. mgr-gitnerd creates PR: gh pr create --base develop --head release/v{NEW} --title "chore(release): bump to v{NEW}" --body "<MUST include 'Closes #N' for EVERY issue this release resolves>"
|
|
333
|
+
⚠ auto-tag.yml closes issues by grep'ing Closes/Fixes/Resolves keywords in the PR BODY — NOT by milestone membership. If the keywords are missing, no issues close and the workflow still reports success (#1531).
|
|
334
|
+
Before creating the PR (whether via inline --body or --body-file), confirm the body text actually contains a Closes line per issue.
|
|
329
335
|
c. mgr-gitnerd merges PR (admin merge required due to branch protection)
|
|
330
336
|
d. DO NOT manually git tag or gh release create.
|
|
331
|
-
auto-tag.yml fires on release/v* PR merge → creates tag → closes linked
|
|
337
|
+
auto-tag.yml fires on release/v* PR merge → creates tag → closes issues linked via PR-body Closes/Fixes/Resolves keywords → closes milestone → deletes release branch.
|
|
332
338
|
release.yml fires on the tag → npm publish + GitHub Release creation.
|
|
333
339
|
Milestone close and issue close are handled downstream by auto-tag.yml — do NOT close them manually.
|
|
340
|
+
After merge, verify each targeted issue is actually CLOSED (gh issue view); close manually if still open. Workflow conclusion=success is not evidence of close (#1531 — v1.1.34 Closes-keyword omission left 5 issues open, manual close required).
|
|
334
341
|
- Non-npm / no auto-tag.yml:
|
|
335
342
|
mgr-gitnerd: git tag v{NEW} && git push origin v{NEW}
|
|
336
343
|
mgr-gitnerd: gh release create v{NEW} (with release notes)
|
package/templates/manifest.json
CHANGED