Website has frequent caching issues

[SuperSandro2000]

Welcome

• [X] Yes, I'm using a binary release within 2 latest releases. Only such installations are supported.
• [X] Yes, I've searched similar issues on GitHub and didn't find any.
• [X] Yes, I've read the typecheck section of the FAQ.
• [X] Yes, I've tried with the standalone linter if available (e.g., gocritic, go vet, etc.).
• [X] I agree to follow this project's Code of Conduct

Description of the problem

Whenever I visit the changelog page from the releases page, I wonder why the changelog for the new version is missing. Sometimes I remember to press F5 and reload the page and then it suddenly appears. I think this is a client side browser caching issue based on wrong cache control header or webworker which only updates the cache on the first visit. I am not really familiar with the inner workings of the website, so I am just guessing.

How to reproduce this:

• Visit https://golangci-lint.run/product/changelog/#1603 today in Chrome
• wait for 1.60.4
• visit https://golangci-lint.run/product/changelog/#1604 and wonder where the section is

Version of golangci-lint

not relevant

Configuration

not relevant

Go environment

not relevant

Verbose output of running

not relevant

A minimal reproducible example or link to a public repository

not relevant

Validation

• [X] Yes, I've included all information above (version, config, etc.).

Supporter

• [ ] I am a sponsor/backer through GitHub or OpenCollective

[boring-cyborg[bot]]

Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors.

[tomarus]

I kinda have the same issue. Sometimes i notice our CI uses a newer version of golangci-lint that produces some new warnings I don't recognize. So i go to the website to copy the install url and install it, only to notice it hasn't changed on my local machine, until i shift-reload or page and see the actual version number change. Might indeed be a small http header caching issue.

[ldez]

We are aware of the problems, we plan to change our documentation generator because the current system is not maintainable and has a lot of flaws. This is something that we are working on but it takes time.