From 8c50ab6e3717c8bc1dbeaaad2a75bdeca6343a87 Mon Sep 17 00:00:00 2001
From: FosterStack Admin <317177128+fosterstack-admin@users.noreply.github.com>
Date: Thu, 8 Oct 2026 20:21:48 -0400
Subject: [PATCH 1/4] Page: long-term support for a build cache, what is
supported today
---
long-term-support-build-cache/index.html | 123 +++++++++++++++++++++++
sitemap.xml | 4 +
2 files changed, 127 insertions(+)
create mode 100644 long-term-support-build-cache/index.html
diff --git a/long-term-support-build-cache/index.html b/long-term-support-build-cache/index.html
new file mode 100644
index 0000000..7629d80
--- /dev/null
+++ b/long-term-support-build-cache/index.html
@@ -0,0 +1,123 @@
+
+
+
+
+
+Long-term support for a build cache: what is supported today
+
+
+
+
+
+
+
+
+
+
fosterstack
+
Infrastructure worth keeping — and kept patched.
+
+
+
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. Fixes are not back-ported to older ones.
+
A fix reaches the free and paid versions on the same day. 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, and nobody runs it in a real build pipeline yet except us.
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, and nobody runs it in a real build pipeline yet except us.
+
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.