Skip to content

fix: 부스 UI 변경 대응#44

Merged
Ogunaru merged 7 commits into
mainfrom
develop
Apr 17, 2026
Merged

fix: 부스 UI 변경 대응#44
Ogunaru merged 7 commits into
mainfrom
develop

Conversation

@Ogunaru

@Ogunaru Ogunaru commented Feb 23, 2026

Copy link
Copy Markdown
Member

아이템 등록 및 업데이트 감지가 제대로 되지 않는 문제 수정

@Ogunaru Ogunaru requested a review from Nopied February 23, 2026 06:24
@Ogunaru Ogunaru self-assigned this Feb 23, 2026
Ogunaru added 2 commits April 17, 2026 08:52
Matched FBX entries by name/hash first, then paired remaining same-name files as changes so unchanged duplicates stop surfacing as noisy add/delete output. Extracted the diff logic into a focused module and added regression coverage for duplicate basename scenarios.

Constraint: FBX-only tracking stores hashes by path but user-facing diffs need stable name-level change reporting
Rejected: Keep basename-only add/delete labeling with index suffixes | still obscures real content changes
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: If path-sensitive semantics are needed later, adjust calculate_fbx_diff instead of reintroducing basename-only display labels
Tested: python3 -m unittest discover -s tests -p 'test_*.py'; python3 -m py_compile booth_checker/__main__.py booth_checker/fbx_diff.py tests/test_fbx_diff.py
Not-tested: End-to-end BOOTH download flow and Discord changelog rendering with real FBX archives
…ushes

Recent workflow changes switched GHCR login from the ephemeral repository
`GITHUB_TOKEN` to a custom `GH_TOKEN` secret. That made registry login depend on
an extra secret and token policy outside the repository defaults, and the build
started failing during `docker/login-action` with `denied: denied`.

This change returns both image publishing workflows to the built-in token path,
which matches GitHub's recommended GHCR setup for packages associated with the
workflow repository.

Constraint: GHCR publishing must work without a separately managed PAT when repository-scoped workflow auth is sufficient
Rejected: Keep `GH_TOKEN` and document secret setup | preserves a brittle dependency and does not address the observed login denial
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: If GHCR push still fails, inspect package linkage and "Manage Actions access" on the existing package before reintroducing a PAT
Tested: YAML parse for `.github/workflows/develop-build.yml` and `.github/workflows/latest-build.yml`
Not-tested: End-to-end GitHub Actions run against GHCR from the hosted runner
@Ogunaru

Ogunaru commented Apr 17, 2026

Copy link
Copy Markdown
Member Author

PR 리뷰 누락 develop으로 계속 사용 시 문제 없어서 PR 진행

@Ogunaru Ogunaru merged commit f9faae3 into main Apr 17, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant