Skip to content

fix: restore docs/logo.svg so cached pi.dev preview reference resolves - #703

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-11_restore-logo-svg
Sep 11, 2026
Merged

fix: restore docs/logo.svg so cached pi.dev preview reference resolves#703
ranxianglei merged 1 commit into
masterfrom
2026-09-11_restore-logo-svg

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Fixes the broken image on https://pi.dev/packages/billion-context (图片加载失败).

Root cause (verified):

  • npm is correct & live: published 0.1.105, pi.image -> docs/logo.png, and that PNG returns HTTP 200 (image/png, 1055148 B).
  • pi.dev's stored record still points at docs/logo.svg (the value from v0.1.104), but fix: serve raster PNG for pi.dev preview image instead of SVG #701 deleted that file -> 404 -> broken image. pi.dev has not re-indexed to 0.1.105 yet and exposes no self-serve re-index button; its preview-media edge cache is only max-age=300.

Fix: restore docs/logo.svg so the currently-cached reference resolves immediately. No new publish needed — raw.githubusercontent.com serves master directly, so within ~5 min the broken image becomes the (older) SVG, and it flips to the hero PNG automatically once pi.dev re-indexes 0.1.105.

Content change, no version bump.

pi.dev's stored record for billion-context still points pi.image at docs/logo.svg (the value as of v0.1.104), but #701 deleted that file -> 404 -> broken image on https://pi.dev/packages/billion-context. npm 0.1.105 already correctly points at docs/logo.png, but pi.dev has not re-indexed to it yet and exposes no self-serve re-index.

Restore the SVG so the currently-cached reference resolves immediately (no new publish needed; raw.githubusercontent.com serves master directly). The hero PNG takes over automatically once pi.dev re-indexes 0.1.105.

Lesson: don't delete an asset that a published version's metadata may still reference.
@ranxianglei ranxianglei mentioned this pull request Sep 11, 2026
@github-actions

Copy link
Copy Markdown

📦 Built Package Artifact

Branch: 2026-09-11_restore-logo-svg (7764d9c)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-703

Each push to this PR publishes a new version under the pr-703 npm tag.

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr703.tgz
npm install -g package

This comment is automatically updated on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Reviewed PR #703 against the code and live endpoints. Verdict: clean, correct, merge-ready.

Bug triage (root cause verified with evidence):

  • npm 0.1.105 is live with pi.image.../master/docs/logo.png, and that PNG returns HTTP 200.
  • fix: serve raster PNG for pi.dev preview image instead of SVG #701 (eb88da9) is what deleted docs/logo.svg (34 lines) and flipped pi.image to logo.png.
  • master/docs/logo.svg currently returns HTTP 404 — so pi.dev's still-cached reference to docs/logo.svg is exactly what breaks the image. Root cause holds.

Diff review:

  • Single file, +34 lines, new-file only — no unrelated changes, no lockfile/whitespace churn, and no version bump (correct: content-only change). Passes the clean-diff gate.
  • The restored docs/logo.svg is byte-identical to the exact file fix: serve raster PNG for pi.dev preview image instead of SVG #701 removed (verified via diff against eb88da9^:docs/logo.svg). We're restoring the known-good original, not a new design.
  • The branch is a single commit sitting directly on the current master tip (merge-base == master tip) — no divergence, no conflict risk.

Why the fix works: pi.dev serves the preview straight from raw.githubusercontent.com/.../master/docs/logo.svg; once merged that path returns 200 again, so the currently-cached reference resolves within its max-age=300 edge window. When pi.dev later re-indexes 0.1.105, pi.image flips to the hero PNG automatically. No new publish needed.

Optional follow-up (non-blocking): after pi.dev has re-indexed 0.1.105, docs/logo.svg can be dropped again. Not required for this hotfix.

I can't merge (human-only per repo rules). Please merge when ready: #703

中文摘要: 该 PR 恢复了被 #701 删除的 docs/logo.svg(与删除前逐字节一致),使 pi.dev 缓存中仍指向该 SVG 的预览图在合并后即刻恢复显示,无需重新发布;diff 干净、单文件、无任何版本号改动,可以合并。

@ranxianglei
ranxianglei merged commit 2c5bf3a into master Sep 11, 2026
6 checks passed
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