Skip to content

armgit / Pulse

Public Imported from GitHub
0

Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.

Distinguish approved stable patches from available updates in Help

pulse-triage[bot]56d9e17db650
diff --git a/docs/AI_TRANSPARENCY.md b/docs/AI_TRANSPARENCY.md
index c455291371..c6597fa64e 100644
--- a/docs/AI_TRANSPARENCY.md
+++ b/docs/AI_TRANSPARENCY.md
@@ -60,12 +60,22 @@ requests are opened by `pulse-triage[bot]` and state what changed, why it
was needed, which reports or demand-ledger entries it answers, and what
validation was used, so the record on GitHub is the record of the decision.
-Stable publication is targeted seven days after the last stable release. The
+Minor stable publication is targeted seven days after the last minor stable release. The
next minor release candidate becomes eligible one day earlier, reserving its
full 24-hour soak; preparation and qualification can move publication later.
It is cut from the head of `main` and carries everything on `main` at that cut,
not a selected set of fixes. Repairs go on `main`, not onto an older release
-line. Patch releases are not scheduled.
+line. A stable patch does not restart the weekly minor clock.
+
+A limited stable-patch path is being added for regressions in the current
+stable release, security vulnerabilities and data loss. **As of 27 October 2026,
+stable patches are not yet available.** Until enabled, repairs reach stable users
+in a containing minor release. Once available, a patch starts from the current
+stable and adds only eligible repairs already merged to `main`, plus release
+metadata and publication support, not every unrelated change on `main`. It does
+not delay or replace the weekly minor cycle. The `stable-regression` label does
+not guarantee a patch or establish availability; see
+[limited stable patches](RELEASE_PROCESS.md#limited-stable-patches).
Between stable releases, daily betas carry new changes from `main`; no beta is
cut within a day of the candidate being due. An important fix ships in the next
diff --git a/docs/RELEASE_PROCESS.md b/docs/RELEASE_PROCESS.md
index 54b4aa516b..f05905926c 100644
--- a/docs/RELEASE_PROCESS.md
+++ b/docs/RELEASE_PROCESS.md
@@ -60,12 +60,12 @@ around the failure by disabling signature verification or replacing the server
with a chart asset. Follow the existing installation's
[signed update route and helper ownership checks](AUTO_UPDATE.md#proxmoxve-lxc-manual).
-## How releases are prepared
+## How minor releases are prepared
Releases follow a fixed schedule rather than individual judgment.
-1. **Cut a candidate from `main`.** Stable publication is targeted **seven days
- after the last stable release**, provided `main` has changed since that release.
+1. **Cut a candidate from `main`.** Minor stable publication is targeted **seven days
+ after the last minor stable release**, provided `main` has changed since that release.
The next release candidate becomes eligible **one day earlier**, reserving the
full 24-hour soak. Preparation and qualification can move publication later.
Nothing brings that cut forward: an important fix ships in the next daily
@@ -81,10 +81,10 @@ Releases follow a fixed schedule rather than individual judgment.
4. **Promote it unchanged.** After a clean soak, the same candidate is promoted to
stable. Release metadata may change, but product content cannot.
-## Cadence and stable promotion
+## Minor cadence and stable promotion
-- Each release is the next minor version: after `6.5.0` comes `6.6.0`. Patch
- releases are not scheduled.
+- The weekly release is the next minor version: after `6.6.0` comes `6.7.0`.
+ A stable patch does not restart this weekly clock.
- Only an open issue labelled `release-blocker` stops a promotion. That label marks
something that worked in the current stable release but is broken in the
candidate. Each such issue is closed once its fix is on `main`. When every one is
@@ -92,7 +92,8 @@ Releases follow a fixed schedule rather than individual judgment.
- Successive candidates for the same version are published at least **24 hours**
apart. Time spent on a beta does not count towards an RC's soak.
- A defect that the current stable release already has is fixed on `main` and ships
- in the next release.
+ in a containing minor release, or an eligible [stable patch](#limited-stable-patches)
+ once that path is available.
Work merged during a candidate's soak waits for the next cycle's betas and
candidate. Only a `release-blocker` requires a fresh candidate; an important fix
@@ -100,6 +101,37 @@ alone does not replace a soaking candidate or bring stable publication forward.
Every replacement still carries everything on `main` at its cut and goes
through the same required checks and full 24-hour soak.
+### Limited stable patches
+
+**As of 27 October 2026, stable patches are not yet available.** Until this path
+is enabled, stable users receive repairs in the next minor release that contains
+them. An approved patch policy, an issue label or a fix on `main` is not an
+available update; check the [published releases](https://github.com/rcourtman/Pulse/releases)
+and the containing version named in the issue reply.
+
+The patch policy is narrower than the weekly minor cycle:
+
+- **Current stable regressions only.** The maintainer applies `stable-regression`
+ when a report establishes that the current stable broke behaviour working in
+ the previous stable, has a security vulnerability or loses data. It is not a
+ fast track for other bugs or feature requests. A regression in a release
+ candidate instead uses `release-blocker`, not `stable-regression`.
+- **Limited contents.** A patch starts from the current stable and adds only
+ eligible repairs already merged to `main`, plus release metadata and
+ publication support. It does not carry every unrelated change on `main`.
+ A repair that cannot be included still reaches users through a containing
+ minor; patch delivery is not guaranteed for every labelled issue.
+- **Separate timing.** For example, a patch after `6.6.0` would be `6.6.1`,
+ first published as an opt-in `6.6.1-rc.1`, then promoted unchanged after its
+ required soak. It never delays or replaces the weekly minor candidate or
+ its soak, and does not move the next minor's date. Only the current stable
+ can be patched; a newer stable ends an unfinished patch for the older one.
+
+You do not need to install a preview to report a stable regression. Describe the
+original failure and any already-observed working version in the existing issue;
+unknown details are valid. Do not downgrade, repeat an unsafe operation or change
+update channels just to establish a baseline.
+
## Taking part in Preview testing
Start with the [published release notes](https://github.com/rcourtman/Pulse/releases).
diff --git a/frontend-modern/public/docs/AI_TRANSPARENCY.md b/frontend-modern/public/docs/AI_TRANSPARENCY.md
index c455291371..c6597fa64e 100644
--- a/frontend-modern/public/docs/AI_TRANSPARENCY.md
+++ b/frontend-modern/public/docs/AI_TRANSPARENCY.md
@@ -60,12 +60,22 @@ requests are opened by `pulse-triage[bot]` and state what changed, why it
was needed, which reports or demand-ledger entries it answers, and what
validation was used, so the record on GitHub is the record of the decision.
-Stable publication is targeted seven days after the last stable release. The
+Minor stable publication is targeted seven days after the last minor stable release. The
next minor release candidate becomes eligible one day earlier, reserving its
full 24-hour soak; preparation and qualification can move publication later.
It is cut from the head of `main` and carries everything on `main` at that cut,
not a selected set of fixes. Repairs go on `main`, not onto an older release
-line. Patch releases are not scheduled.
+line. A stable patch does not restart the weekly minor clock.
+
+A limited stable-patch path is being added for regressions in the current
+stable release, security vulnerabilities and data loss. **As of 27 October 2026,
+stable patches are not yet available.** Until enabled, repairs reach stable users
+in a containing minor release. Once available, a patch starts from the current
+stable and adds only eligible repairs already merged to `main`, plus release
+metadata and publication support, not every unrelated change on `main`. It does
+not delay or replace the weekly minor cycle. The `stable-regression` label does
+not guarantee a patch or establish availability; see
+[limited stable patches](RELEASE_PROCESS.md#limited-stable-patches).
Between stable releases, daily betas carry new changes from `main`; no beta is
cut within a day of the candidate being due. An important fix ships in the next
diff --git a/frontend-modern/public/docs/RELEASE_PROCESS.md b/frontend-modern/public/docs/RELEASE_PROCESS.md
index 54b4aa516b..f05905926c 100644
--- a/frontend-modern/public/docs/RELEASE_PROCESS.md
+++ b/frontend-modern/public/docs/RELEASE_PROCESS.md
@@ -60,12 +60,12 @@ around the failure by disabling signature verification or replacing the server
with a chart asset. Follow the existing installation's
[signed update route and helper ownership checks](AUTO_UPDATE.md#proxmoxve-lxc-manual).
-## How releases are prepared
+## How minor releases are prepared
Releases follow a fixed schedule rather than individual judgment.
-1. **Cut a candidate from `main`.** Stable publication is targeted **seven days
- after the last stable release**, provided `main` has changed since that release.
+1. **Cut a candidate from `main`.** Minor stable publication is targeted **seven days
+ after the last minor stable release**, provided `main` has changed since that release.
The next release candidate becomes eligible **one day earlier**, reserving the
full 24-hour soak. Preparation and qualification can move publication later.
Nothing brings that cut forward: an important fix ships in the next daily
@@ -81,10 +81,10 @@ Releases follow a fixed schedule rather than individual judgment.
4. **Promote it unchanged.** After a clean soak, the same candidate is promoted to
stable. Release metadata may change, but product content cannot.
-## Cadence and stable promotion
+## Minor cadence and stable promotion
-- Each release is the next minor version: after `6.5.0` comes `6.6.0`. Patch
- releases are not scheduled.
+- The weekly release is the next minor version: after `6.6.0` comes `6.7.0`.
+ A stable patch does not restart this weekly clock.
- Only an open issue labelled `release-blocker` stops a promotion. That label marks
something that worked in the current stable release but is broken in the
candidate. Each such issue is closed once its fix is on `main`. When every one is
@@ -92,7 +92,8 @@ Releases follow a fixed schedule rather than individual judgment.
- Successive candidates for the same version are published at least **24 hours**
apart. Time spent on a beta does not count towards an RC's soak.
- A defect that the current stable release already has is fixed on `main` and ships
- in the next release.
+ in a containing minor release, or an eligible [stable patch](#limited-stable-patches)
+ once that path is available.
Work merged during a candidate's soak waits for the next cycle's betas and
candidate. Only a `release-blocker` requires a fresh candidate; an important fix
@@ -100,6 +101,37 @@ alone does not replace a soaking candidate or bring stable publication forward.
Every replacement still carries everything on `main` at its cut and goes
through the same required checks and full 24-hour soak.
+### Limited stable patches
+
+**As of 27 October 2026, stable patches are not yet available.** Until this path
+is enabled, stable users receive repairs in the next minor release that contains
+them. An approved patch policy, an issue label or a fix on `main` is not an
+available update; check the [published releases](https://github.com/rcourtman/Pulse/releases)
+and the containing version named in the issue reply.
+
+The patch policy is narrower than the weekly minor cycle:
+
+- **Current stable regressions only.** The maintainer applies `stable-regression`
+ when a report establishes that the current stable broke behaviour working in
+ the previous stable, has a security vulnerability or loses data. It is not a
+ fast track for other bugs or feature requests. A regression in a release
+ candidate instead uses `release-blocker`, not `stable-regression`.
+- **Limited contents.** A patch starts from the current stable and adds only
+ eligible repairs already merged to `main`, plus release metadata and
+ publication support. It does not carry every unrelated change on `main`.
+ A repair that cannot be included still reaches users through a containing
+ minor; patch delivery is not guaranteed for every labelled issue.
+- **Separate timing.** For example, a patch after `6.6.0` would be `6.6.1`,
+ first published as an opt-in `6.6.1-rc.1`, then promoted unchanged after its
+ required soak. It never delays or replaces the weekly minor candidate or
+ its soak, and does not move the next minor's date. Only the current stable
+ can be patched; a newer stable ends an unfinished patch for the older one.
+
+You do not need to install a preview to report a stable regression. Describe the
+original failure and any already-observed working version in the existing issue;
+unknown details are valid. Do not downgrade, repeat an unsafe operation or change
+update channels just to establish a baseline.
+
## Taking part in Preview testing
Start with the [published release notes](https://github.com/rcourtman/Pulse/releases).
diff --git a/frontend-modern/src/features/docs/__tests__/issueFollowThroughGuide.test.ts b/frontend-modern/src/features/docs/__tests__/issueFollowThroughGuide.test.ts
index 7d5422a71c..3e2b2958c9 100644
--- a/frontend-modern/src/features/docs/__tests__/issueFollowThroughGuide.test.ts
+++ b/frontend-modern/src/features/docs/__tests__/issueFollowThroughGuide.test.ts
@@ -6,7 +6,12 @@ import { renderDocMarkdown, stripLeadingTitle } from '../docMarkdown';
const repoRoot = path.resolve(path.dirname(fileURLToPath(import.meta.url)), '../../../../..');
const shippedDocs = path.join(repoRoot, 'frontend-modern/public/docs');
-const source = readFileSync(path.join(shippedDocs, 'AI_TRANSPARENCY.md'), 'utf8');
+const readGuide = (name: string) =>
+ readFileSync(
+ process.env[`PULSE_${name}_GUIDE_TEST_INPUT`] ?? path.join(shippedDocs, `${name}.md`),
+ 'utf8',
+ );
+const source = readGuide('AI_TRANSPARENCY');
function renderGuide(name: string, markdown: string): HTMLElement {
const article = document.createElement('article');
@@ -83,7 +88,7 @@ describe('public issue follow-through guidance', () => {
const article = renderGuide('AI_TRANSPARENCY', source);
const text = prose(article);
expect(text).toContain(
- 'Stable publication is targeted seven days after the last stable release',
+ 'Minor stable publication is targeted seven days after the last minor stable release',
);
expect(text).toContain('one day earlier, reserving its full 24-hour soak');
expect(text).toContain(
@@ -95,7 +100,7 @@ describe('public issue follow-through guidance', () => {
expect(
article.querySelector('a[href="/docs/RELEASE_PROCESS"]')?.hasAttribute('data-doc-link'),
).toBe(true);
- const releaseSource = readFileSync(path.join(shippedDocs, 'RELEASE_PROCESS.md'), 'utf8');
+ const releaseSource = readGuide('RELEASE_PROCESS');
expect(releaseSource).toBe(
readFileSync(path.join(repoRoot, 'docs/RELEASE_PROCESS.md'), 'utf8'),
);
@@ -105,4 +110,38 @@ describe('public issue follow-through guidance', () => {
expect(prose(release)).toContain('Only a release-blocker requires a fresh candidate');
expect(prose(release)).not.toContain('can bring');
});
+
+ it('makes the unavailable patch path and limited contents explicit in both consumed guides', () => {
+ for (const name of ['AI_TRANSPARENCY', 'RELEASE_PROCESS']) {
+ const article = renderGuide(name, readGuide(name));
+ const text = prose(article);
+ expect(text).toContain('As of 27 October 2026, stable patches are not yet available');
+ expect(text).toContain('containing minor release');
+ expect(text).toContain('eligible repairs already merged to main');
+ expect(text).toContain('release metadata and publication support');
+ expect(text).toContain('stable-regression');
+ expect(text).not.toContain('Patch releases are not scheduled');
+ }
+ });
+
+ it('links the public triage disclosure to the actual scoped patch guidance', () => {
+ const article = renderGuide('AI_TRANSPARENCY', source);
+ const link = article.querySelector<HTMLAnchorElement>(
+ 'a[href="/docs/RELEASE_PROCESS#limited-stable-patches"]',
+ );
+ expect(link?.textContent).toBe('limited stable patches');
+ expect(link?.hasAttribute('data-doc-link')).toBe(true);
+ const release = renderGuide('RELEASE_PROCESS', readGuide('RELEASE_PROCESS'));
+ const heading = release.querySelector(new URL(link!.href).hash);
+ expect(heading?.tagName).toBe('H3');
+ const status = heading!.nextElementSibling;
+ expect(status?.querySelector('strong')?.textContent).toBe(
+ 'As of 27 October 2026, stable patches are not yet available.',
+ );
+ expect(prose(status!)).toContain('is not an available update');
+ expect(prose(release)).toContain('A stable patch does not restart this weekly clock');
+ expect(prose(release)).toContain('does not move the next minor');
+ expect(prose(release)).toContain('patch delivery is not guaranteed for every labelled issue');
+ expect(prose(release)).toContain('Do not downgrade, repeat an unsafe operation');
+ });
});
diff --git a/scripts/tests/test_transparency_docs.py b/scripts/tests/test_transparency_docs.py
index 4283634c54..f66ec30938 100644
--- a/scripts/tests/test_transparency_docs.py
+++ b/scripts/tests/test_transparency_docs.py
@@ -23,7 +23,7 @@ class TransparencyDocsTest(unittest.TestCase):
def test_all_main_minor_cycle_not_selective_backports(self):
for path, text in self.documents():
with self.subTest(document=path):
- self.assertIn("Stable publication is targeted seven days after the last stable release", text)
+ self.assertIn("Minor stable publication is targeted seven days after the last minor stable release", text)
self.assertIn("next minor release candidate becomes eligible one day earlier", text)
self.assertIn("reserving its full 24-hour soak", text)
self.assertIn("preparation and qualification can move publication later", text)
@@ -32,7 +32,8 @@ class TransparencyDocsTest(unittest.TestCase):
self.assertIn("Repairs go on `main`, not onto an older release line", text)
self.assertIn("An important fix ships in the next beta, not through an early candidate or stable release", text)
self.assertIn("no beta is cut within a day of the candidate being due", text)
- self.assertIn("Patch releases are not scheduled", text)
+ self.assertIn("A stable patch does not restart the weekly minor clock", text)
+ self.assertNotIn("Patch releases are not scheduled", text)
self.assertNotIn("takes only backports", text)
self.assertNotIn("Every 14 days", text)
self.assertNotIn("An early cut can bring", text)
@@ -42,7 +43,7 @@ class TransparencyDocsTest(unittest.TestCase):
path = ROOT / directory / "RELEASE_PROCESS.md"
text = " ".join(path.read_text(encoding="utf-8").split()).replace("**", "")
with self.subTest(document=path):
- self.assertIn("seven days after the last stable release", text)
+ self.assertIn("seven days after the last minor stable release", text)
self.assertIn("one day earlier", text)
self.assertIn("Nothing brings that cut forward", text)
self.assertIn("an important fix ships in the next daily beta", text)
@@ -51,6 +52,38 @@ class TransparencyDocsTest(unittest.TestCase):
self.assertIn("same required checks and full 24-hour soak", text)
self.assertNotIn("can bring", text)
+ def test_patch_policy_is_not_claimed_as_available_delivery(self):
+ for directory in ("docs", "frontend-modern/public/docs"):
+ for name in ("AI_TRANSPARENCY", "RELEASE_PROCESS"):
+ path = ROOT / directory / f"{name}.md"
+ text = " ".join(path.read_text(encoding="utf-8").split()).replace("**", "")
+ with self.subTest(document=path):
+ self.assertIn("As of 27 October 2026, stable patches are not yet available", text)
+ self.assertIn("stable-regression", text)
+ self.assertIn("eligible repairs already merged to `main`", text)
+ self.assertIn("release metadata and publication support", text)
+ self.assertIn("containing minor release", text)
+ self.assertNotIn("Patch releases are not scheduled", text)
+
+ def test_patch_guide_distinguishes_eligibility_cadence_and_safe_reporting(self):
+ for directory in ("docs", "frontend-modern/public/docs"):
+ path = ROOT / directory / "RELEASE_PROCESS.md"
+ text = " ".join(path.read_text(encoding="utf-8").split()).replace("**", "")
+ with self.subTest(document=path):
+ for claim in (
+ "current stable broke behaviour working in the previous stable",
+ "security vulnerability or loses data",
+ "not a fast track for other bugs or feature requests",
+ "patch delivery is not guaranteed for every labelled issue",
+ "promoted unchanged after its required soak",
+ "never delays or replaces the weekly minor candidate",
+ "does not move the next minor's date",
+ "Only the current stable can be patched",
+ "You do not need to install a preview to report a stable regression",
+ "Do not downgrade, repeat an unsafe operation or change update channels",
+ ):
+ self.assertIn(claim, text)
+
def test_blockers_need_a_fresh_candidate_not_a_changed_soak(self):
for path, text in self.documents():
with self.subTest(document=path):