Add update access setup flows - #11
Conversation
Deploying pie-menu-editor-website with
|
| Latest commit: |
55d1f9f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4bf55fce.pie-menu-editor-website.pages.dev |
| Branch Preview URL: | https://website-update-access-setup.pie-menu-editor-website.pages.dev |
|
@codex security review |
|
@codex security review |
|
@codex security review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 61c6b53dd2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex security review |
|
Security review completed. No security issues were found in this pull request. Reviewed commit: Only the user who started this review can view the report in Codex. ℹ️ About Codex security reviews in GitHubThis is an experimental Codex feature. Security reviews are triggered when:
Once complete, Codex will leave suggestions, or a comment if no findings are found. |
概要 setup専用クライアントへ、既存の初回claimに加えて次の操作を追加します。 - 1年分のUpdate Extension適用 - server-side update accessの確認 - Recovery secretによるRepository accessの置換 初回offerは購入ページ側の固定linkから公開offer codeを渡し、購入者が期間やpolicyを入力するUIは設けません。 ## Security / privacy境界 - purchase key、Recovery secret、Repository tokenをbrowser storageやURLへ保存しない - claim/renewal/reissueの再試行IDだけを8日間保持する - statusはread-onlyで再試行IDを保持しない - reissue後のone-time credential deliveryと明示acknowledgementは既存機構を再利用する - CSP、SRI、exact-origin、no-store、noindexを維持する - service responseはbounded parserを通し、statusとupdates-through以外の内部情報を表示しない ## 検証 -
npm test(19 tests) -node --check dist/setup/app.mjs-git diff --check- local browserで初期画面、4操作selector、responsive layoutを目視確認 ## Landing note このrepositoryはmainmergeでCloudflare Pagesへ自動deployされます。service側C5Aがproductionへcutoverされる前にこのPRをmergeしません。Security Review CLEANとrequired checksを取得した後、C6のcutover順序に従って待機させます。