CircleCI orbs that have published new versions in the last couple of days are showing outdated badges on GitHub. It looks like something is going wrong with caching when fetching badges from https://badges.circleci.com/orbs
The response header from https://badges.circleci.com/orbs/circleci/path-filtering.svg contains no Cache-Control
Compare to build status from https://circleci.com/gh/CircleCI-Public/path-filtering-orb.svg?style=shield where Cache-Control returns with max-age=60 (unit is seconds)
This relates to New Orb Version Badge Endpoint
If it’s not possible to fix the badge updating correctly, I would probably want to remove the badge instead of leaving it there with a misleading value.
Is there anybody available who can comment, or, better still, fix the issue?
It’s possible to “bust the cache” with a dummy query like https://badges.circleci.com/orbs/circleci/path-filtering.svg?v=1
however unless the badge starts returning Cache-Control it will be necessary to bust the cache for every subsequent release, which defeats the purpose of having a badge which self-updates.
I found that it is possible to purge the cache with
curl -X PURGE https://camo.githubusercontent.com/<image-id>
This is a workaround.
I sent a cache purge message to circleci/path-filtering to get it to display the current orb version 1.3.0. Again, this is a temporary workaround.
To see the update, you may need to refresh your browser cache, for instance with Ctrl-F5.
