Long-term support for a build cache: what is supported today
+"LTS" means a version that keeps getting fixes for a stated period, so you can stay on it. Here is what that means for FosterStack Cache today, with no promises beyond what exists.
+ +What is supported today
+The latest minor release. That is the whole policy for now, and our security policy says so. There is no separate long-term-support line yet, no list of older versions that get fixes, and no support period to quote.
+ +What that means for you
+-
+
- To get a fix, move to the latest release. Older releases are not on the supported list. +
- Security patches are never withheld from the free tier. +
- We aim to ship fixes for dependency vulnerabilities within 48 hours of public disclosure. That is a target, not a promise. +
- Every published image is rescanned daily, so a vulnerability disclosed against something we already shipped raises an issue. +
How to run it with that in mind
+-
+
- Pin the image to an exact version or digest, not
latest, so a deploy never changes without you choosing it.
+ - Upgrade on a routine. A build cache is disposable, so an upgrade that goes wrong costs you slower builds while it refills, not lost work. +
- Watch the repository's releases on GitHub. It is the one notice channel, and you can stop at any time. We do not collect email. +
What we are not saying
+We are not announcing an LTS line, a support period, or a date. If one ever exists, it will be described here, in present tense, once it ships. The project is early.
+ +Related: how releases are built and signed and what to check in a replacement build cache.
+ +