After uploading the updated version of any file relevant to the layout of your website (CSS, JS or even images), the version displayed on the front-end may not be the latest one.

This happens while the template is cached. The request to these files is made with a versioning parameter, in which its value is a timestamp of the original file - for example, /arquivos/style.css?v=636492689128330000. As long as the timestamp is the same, the file will also remain the same.

The main cause of this scenario is that the template doesn't know that a file has been changed, so updating the files is not enough for its cache to expire.

In a given template, update a CSS or Javascript file, uploading it again with the same name, so that it overwrites the old one.

Note that the timestamp parameter in the request will not change, and the contents of the file will be the same.

Changing the templates that call the updated files is enough to update the timestamp, which will then bring the latest version of the files.

One suggestion to make the workaround easier every time you change a layout file is to create a version control subtemplate that is present in all the templates used in the store. For the content of this subtemplate an HTML comment will suffice, with information that will be updated with each new version of the files.

When the subtemplate is changed, all the templates that read it will be updated, along with the files.