Badge from CELPA is stuck

[jcs090218]

Hmm... I have recently added the badge on my origami.el README page with the following markdown code.

[![CELPA](https://celpa.conao3.com/packages/origami-badge.svg)](https://celpa.conao3.com/#/origami)

It renders but version is still stuck in the previous version timestamp.

After navigating through the url https://celpa.conao3.com/packages/origami-badge.svg, the version should be 20210314.1237 but it shows 20210311.1605 on GitHub. Would this be the issue from GitHub? 😖

[conao3]

I found this issue. As adding some query parameter like ?service=github, disable cache and fetch latest badges.
But celpa.conao3.com currently hosted on very cheap server, I cannot estimate the capabilities of the server.
Maybe we prepare just json and user generate cool badge using shields.io dynamic badge feature?

[jcs090218]

Maybe we prepare just json and user generate cool badge using shields.io dynamic badge feature?

This may work. I was wondering how MELPA achieve this? I think without ?service=github but we are still able to get the latest badges from MELPA.

[jcs090218]

Related discussion is here, melpa/melpa#2231.

We might need to set the header with no cache with in the Apache config file? See, https://stackoverflow.com/questions/11532636/how-to-prevent-http-file-caching-in-apache-httpd-mamp.