CritasWang opened a new pull request, #31:
URL: https://github.com/apache/iotdb-client-nodejs/pull/31

   The `Node.js Version` badge at the top of `README.md` / `README_zh.md` does 
not show up:
   
   ```markdown
   [![Node.js 
Version](https://img.shields.io/node/v/@iotdb/client.svg)](https://nodejs.org/)
   ```
   
   ### Root cause
   
   The badge is a *dynamic* shields.io badge: it looks the package up on the 
npm registry. That exact URL was first fetched while `@iotdb/client` did not 
exist yet (before the 2.0.11 publish), so shields.io answered with a `not 
found` badge and that answer got cached by shields.io's CDN (`cache-control: 
max-age=300`), by GitHub's camo image proxy, and by browsers. Republishing does 
not invalidate those caches because they are keyed on the URL.
   
   ### Fix
   
   Use the canonical shields.io URL and drop the redundant `.svg` suffix. That 
produces a new cache key, so every layer re-fetches the badge. The `License` 
and `npm version` badges are left alone (the npm one already resolves to 
`v2.0.11`; their URLs work).
   
   ### Verification
   
   - `https://img.shields.io/node/v/@iotdb/client` -> HTTP 200, 
`image/svg+xml`, renders `node >= 14.0.0`
   - `https://img.shields.io/node/v/@iotdb/client.svg` (old URL) -> also HTTP 
200 now, i.e. the registry side is healthy; only the cached copy was stale
   - GitHub rendering re-checked in a real browser: the three badges load with 
sizes 88x20 (license), 88x20 (npm version) and 100x20 (Node.js Version)
   
   If a stale badge is still visible after this, a hard refresh 
(Cmd/Ctrl+Shift+R) clears the browser copy.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to