Skip to content

fix: specify the cache-control for badges #474

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 3, 2024

Conversation

LitoMore
Copy link
Contributor

@LitoMore LitoMore commented May 2, 2024

Fixes #341

I used the same value 300 as shields.io's npm version badge.

@LitoMore LitoMore force-pushed the set-cache-control branch from b127dcc to ed805aa Compare May 2, 2024 13:40
Copy link
Member

@lucacasonato lucacasonato left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@marvinhagemeister marvinhagemeister added this pull request to the merge queue May 3, 2024
Merged via the queue into jsr-io:main with commit 105f355 May 3, 2024
6 checks passed
@LitoMore LitoMore deleted the set-cache-control branch May 3, 2024 12:37
@dsherret
Copy link
Member

dsherret commented May 5, 2024

Seems to be fixed. Thanks!

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.

GitHub seems to cache badges
4 participants