fix(landing): redirect /privacy → /policy to unblock CWS extension publish - #4
Merged
Conversation
The Chrome Web Store has https://knowcap.ai/privacy registered as the Knowcap extension's privacy URL, but the actual privacy policy page lives at /policy (built in 988833f, never at /privacy). Google's publish-time reachability check 404s on the URL and blocks every extension publish with: "Publish condition not met: Privacy policy link is not reachable." This has been silently breaking publishes since 1.21.6 (May 6) — 1.21.19 has been sitting unpublished in the CWS dashboard for days. Fix: Next.js permanent redirects for /privacy and /privacy-policy → /policy. Both URLs now return 200 (via 308), Google's check passes, and anyone googling "knowcap privacy" also lands on the policy.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe PR adds an ChangesPrivacy Policy Redirects
Estimated code review effort🎯 2 (Simple) | ⏱️ ~5 minutes Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Chrome Web Store has `https://knowcap.ai/privacy\` registered as the
Knowcap extension's privacy URL, but the actual privacy policy page
lives at `/policy` (created in 988833f, never at /privacy). Google's
publish-time reachability check 404s on the URL and blocks every
extension publish with:
```
"Publish condition not met: Privacy policy link is not reachable."
```
Has silently blocked every extension publish since 1.21.6 (May 6).
1.21.19 has been sitting unpublished in the CWS dashboard for days.
Fix
Next.js permanent redirects `/privacy` and `/privacy-policy` → `/policy`
in `next.config.js`. Both URLs now return 200 (via 308), Google's
reachability check passes, and anyone googling "knowcap privacy" also
lands on the policy.
Test Plan
```
curl -s "https://clients2.google.com/service/update2/crx?response=updatecheck&prodversion=120.0&acceptformat=crx3&x=id%3Dmdcodkbhabjcmbajfmapfiimlkeheche%26v%3D0.0.1%26uc" | grep -oP 'version="[^"]+"'
```
Summary by CodeRabbit
/privacyand/privacy-policyto/policy.