This actually does two things: client caching and server caching
Client caching considers only static files, for which we instruct the web browser to revalidate each cache usage with our server to ensure that it's up-to-date.
Server caching with those settings actually doesn't work (nothing to do), but may in the future as lack of no-store means that server is technically allowed to cache I/O read files for as long as it can guarantee they didn't change on the disk.
In theory, this is required only in specific proxy/CDN solutions accessing ASF data over http that would somehow want to transform the responses
https://github.com/JustArchiNET/ASF-ui/pull/1470
While floating tags are nice to use and fancy, we already had situations where the fixed source code did not result in the same deterministic build as the one built e.g. a week ago due to non-pinned versions that resulted in a different set of dependencies than originally.
Since GitHub actions follow similar pattern, we want to do our best to ensure that if CI in given fixed version passed on a fixed source, then it should also result in the same deterministic output. Of course this is impossible to achieve in 100% (e.g. resources no longer being available over the network), but this is something we can do.
It wasn't like that before renovate since we didn't have a standarized bot that could handle bumping those versions for us.
* implement split on newlines
* replace test of splitting on newlines
* sugar-sugar syntax
* Revert "sugar-sugar syntax"
This reverts commit ee9b558faf.
* add test to confirm that paragraph character size is less or equal to continuation character size
