Prepare v6.3.0-rc.3 release

Contract-Neutral: Routine release-preparation cut for v6.3.0-rc.3. deployment-installability.md IS staged with the substantive active-prerelease and mobile-decision updates for this cut. The residual demand is a verification artifact, and the registry-listed proof scripts/installtests/build_release_assets_test.go plus install_docker_sh_test.go already cover this change and pass against it; they validate the packet dynamically from the repo-root VERSION rather than pinning a literal, so they have no diff to stage. Both were run green immediately before this commit and caught two real errors in the mobile-decision clauses, which are fixed here.
This commit is contained in:
rcourtman
2026-08-18 22:36:10 +01:00
parent 4a66072c15
commit 2f6f2396b6
11 changed files with 57 additions and 34 deletions
+1 -1
View File
@@ -1 +1 @@
6.3.0-rc.2
6.3.0-rc.3
+4 -4
View File
@@ -2,9 +2,9 @@ apiVersion: v2
name: pulse
description: Helm chart for deploying the Pulse hub and optional Docker, Kubernetes, or OpenShift monitoring agent.
type: application
version: 6.3.0-rc.2
appVersion: "6.3.0-rc.2"
icon: https://raw.githubusercontent.com/rcourtman/Pulse/v6.3.0-rc.2/docs/images/pulse-logo.svg
version: 6.3.0-rc.3
appVersion: "6.3.0-rc.3"
icon: https://raw.githubusercontent.com/rcourtman/Pulse/v6.3.0-rc.3/docs/images/pulse-logo.svg
keywords:
- monitoring
- proxmox
@@ -32,7 +32,7 @@ annotations:
description: Smoke tests with kind cluster deployment
artifacthub.io/links: |
- name: Documentation
url: https://github.com/rcourtman/Pulse/blob/v6.3.0-rc.2/docs/KUBERNETES.md
url: https://github.com/rcourtman/Pulse/blob/v6.3.0-rc.3/docs/KUBERNETES.md
- name: Support
url: https://github.com/rcourtman/Pulse/discussions
artifacthub.io/maintainers: |
+1 -1
View File
@@ -1,6 +1,6 @@
# pulse
![Version: 6.3.0-rc.2](https://img.shields.io/badge/Version-6.3.0--rc.2-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 6.3.0-rc.2](https://img.shields.io/badge/AppVersion-6.3.0--rc.2-informational?style=flat-square)
![Version: 6.3.0-rc.3](https://img.shields.io/badge/Version-6.3.0--rc.3-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 6.3.0-rc.3](https://img.shields.io/badge/AppVersion-6.3.0--rc.3-informational?style=flat-square)
Helm chart for deploying the Pulse hub and optional Docker, Kubernetes, or OpenShift monitoring agent.
+1 -1
View File
@@ -2,7 +2,7 @@ version: '3.8'
services:
pulse:
image: ${PULSE_IMAGE:-rcourtman/pulse:6.3.0-rc.2}
image: ${PULSE_IMAGE:-rcourtman/pulse:6.3.0-rc.3}
container_name: pulse
restart: unless-stopped
logging:
+2 -2
View File
@@ -8,8 +8,8 @@ For historical v4 notes that previously lived in this repo, see:
For the current v6 release candidate packet (the current v6 support release
candidate packet), see:
- `docs/releases/RELEASE_NOTES_v6.3.0-rc.2.md`
- `docs/releases/V6_CHANGELOG_v6.3.0-rc.2.md`
- `docs/releases/RELEASE_NOTES_v6.3.0-rc.3.md`
- `docs/releases/V6_CHANGELOG_v6.3.0-rc.3.md`
For the current stable v6 packet, see:
- `docs/releases/RELEASE_NOTES_v6.2.1.md`
+2 -2
View File
@@ -4,8 +4,8 @@ This guide covers practical upgrade steps for existing Pulse installs moving to
For the current v6 release candidate packet, see:
- `docs/releases/RELEASE_NOTES_v6.3.0-rc.2.md`
- `docs/releases/V6_CHANGELOG_v6.3.0-rc.2.md`
- `docs/releases/RELEASE_NOTES_v6.3.0-rc.3.md`
- `docs/releases/V6_CHANGELOG_v6.3.0-rc.3.md`
For the current stable v6 packet, see:
@@ -1447,9 +1447,9 @@ diagnostics. The same release workflow also executes the generated self-signed
and custom-CA Windows installer commands through Windows PowerShell 5.1 before
release assembly, so the first HTTPS fetch is release proof rather than a
string-shape assertion.
The active prerelease `v6.3.0-rc.2` cut sets the repo-root `VERSION`,
The active prerelease `v6.3.0-rc.3` cut sets the repo-root `VERSION`,
repo-root `docker-compose.yml` image default, `scripts/install-docker.sh`
fallback, and Helm chart release metadata to the same `6.3.0-rc.2` release
fallback, and Helm chart release metadata to the same `6.3.0-rc.3` release
version. It follows stable `v6.2.1`, opens the published 6.3 candidate line, uses
`rollback_version=v6.2.1`, and keeps stable/latest pointers on `v6.2.1`. This
candidate establishes the new minor-release packet with durable scoped Patrol
@@ -1460,7 +1460,7 @@ Patrol inbox, first-class Actions workspace, canonical platform-admission
projection, and bounded concurrent unified-resource hydration. Subscription-backed
Patrol turns bound command cleanup after an idle deadline so descendant-held
output pipes cannot extend the caller-owned stall budget. The changes since
`v6.3.0-rc.1` do not require a Pulse Mobile client change and preserve the
`v6.3.0-rc.2` do not require a Pulse Mobile client change and preserve the
existing mobile, Relay, onboarding, and mobile-facing API contracts, so the
server cut is classified `no-mobile-impact`; no companion upload or public
mobile-store rollout is part of this candidate.
@@ -1746,8 +1746,8 @@ For the active stable `v6.1.2` cut, the repo-root compose default and
`scripts/install-docker.sh` fallback must both pin `6.1.2` whenever the
governed `VERSION` is that stable cut. The stable promotion guard remains in
force and rejects leftover `-rc.` defaults.
For the active prerelease `v6.3.0-rc.2` cut, the repo-root compose default and
`scripts/install-docker.sh` fallback must both pin `6.3.0-rc.2`
For the active prerelease `v6.3.0-rc.3` cut, the repo-root compose default and
`scripts/install-docker.sh` fallback must both pin `6.3.0-rc.3`
until the next governed stable cut moves them forward. Each new release moves
these two pins together with the repo-root `VERSION` and the Helm chart metadata
in the same commit; a cut that leaves any of the four on a superseded value is a
@@ -1,12 +1,15 @@
# Pulse v6.3.0-rc.2 Release Notes
# Pulse v6.3.0-rc.3 Release Notes
`v6.3.0-rc.2` is a release candidate for the next Pulse v6 minor release and
the first published candidate in the 6.3 line. An earlier `rc.1` publication
did not complete, so this cut uses a fresh immutable version for the advanced
`main` branch. It follows stable
`v6.2.1` and introduces the Patrol v2 operating model, a first-class Actions
workspace, guarded agent action preflight, large-estate response improvements,
and monitoring correctness fixes.
`v6.3.0-rc.3` is a release candidate for the next Pulse v6 minor release,
following `v6.3.0-rc.2` in the 6.3 line and stable `v6.2.1`. It carries the
Patrol v2 operating model, a first-class Actions workspace, guarded agent
action preflight, large-estate response improvements, and monitoring
correctness fixes.
This candidate adds a group of alert-delivery repairs. Production telemetry
showed installs with a configured notification destination that had never
delivered anything and had no way to find out, because the channel that would
carry such a warning is the one that had failed.
## Highlights
@@ -16,6 +19,13 @@ and monitoring correctness fixes.
without granting mutation authority.
- Approved actions gain agent preflight and stable refusal telemetry; large
installations gain compressed APIs and indexed lookups.
- Pulse now raises an alert about itself when notification delivery is failing,
so a dead notification channel is visible in the alert list and navigation
badge rather than only on a configuration tab.
- The notifications surface says when delivery is paused, and says plainly that
a successful test send does not prove live alerts are getting through.
- The alert flapping cooldown now suppresses for its configured duration
instead of ending as soon as the measurement window drained.
## Added
@@ -95,7 +105,7 @@ and monitoring correctness fixes.
## Upgrade Notes
Use the normal v6 install or update flow for `v6.3.0-rc.2` only when you are
Use the normal v6 install or update flow for `v6.3.0-rc.3` only when you are
comfortable testing a release candidate. The rollback target is `v6.2.1`.
The exact rollback reinstall command is:
@@ -104,7 +114,7 @@ The exact rollback reinstall command is:
./scripts/install.sh --version v6.2.1
```
The changes since `v6.3.0-rc.1` do not require a Pulse Mobile client change
The changes since `v6.3.0-rc.2` do not require a Pulse Mobile client change
and preserve the existing mobile, Relay, onboarding, and mobile-facing API
contracts. No companion mobile build upload or public mobile-store rollout is
part of this candidate.
@@ -1,7 +1,7 @@
# Pulse v6.3.0-rc.2
# Pulse v6.3.0-rc.3
_This changelog describes the changes since `v6.3.0-rc.1` and carries forward
the complete cumulative 6.3 packet since stable `v6.2.1`. `v6.3.0-rc.2` is a
_This changelog describes the changes since `v6.3.0-rc.2` and carries forward
the complete cumulative 6.3 packet since stable `v6.2.1`. `v6.3.0-rc.3` is a
prerelease and rolls back to stable `v6.2.1`._
## Added
@@ -16,6 +16,9 @@ prerelease and rolls back to stable `v6.2.1`._
changes, prerequisites, contract failures, capability limits, policy, and
stale plans.
- Production security guidance and a reusable security-review evidence packet.
- System-scoped alerts, so Pulse can report a fault in itself rather than only
in a monitored resource. Broken notification delivery is the first, raised as
an ordinary alert so it reaches the alert list and navigation badge.
## Changed
@@ -54,6 +57,16 @@ prerelease and rolls back to stable `v6.2.1`._
member addressing, and discovery-analysis timeout handling now use canonical
runtime facts.
- Informational and bodyless HTTP responses remain valid when gzip is enabled.
- The notifications surface states when alert delivery is paused, including
that a passing test send does not prove live alerts are getting through.
Configured destinations were previously silent with no indication.
- Degraded notification delivery is reported on the alerts overview instead of
only on the destinations configuration tab.
- The flapping cooldown now suppresses for its configured duration. It was
recorded and never read, so suppression ended as soon as the sliding window
drained and a resource oscillating just under the threshold was never damped.
- Mobile tables keep narrow values readable, preserve compact replication
values, and use a consistent density across platform surfaces.
## Security
@@ -66,7 +79,7 @@ prerelease and rolls back to stable `v6.2.1`._
## Release Metadata
- Version: `v6.3.0-rc.2`
- Version: `v6.3.0-rc.3`
- Previous release: `v6.2.1`
- Previous stable: `v6.2.1`
- Rollback target: `v6.2.1`
@@ -76,6 +89,6 @@ prerelease and rolls back to stable `v6.2.1`._
- Windows signing decision: the standing prerelease path publishes exact-SHA,
checksum, and detached-signature verified Windows agents without
Authenticode; stable `v6.3.0` restores mandatory SignPath signing
- Mobile decision: `no-mobile-impact`; changes since `v6.3.0-rc.1` preserve the
- Mobile decision: `no-mobile-impact`; changes since `v6.3.0-rc.2` preserve the
existing mobile, Relay, onboarding, and mobile-facing API contracts, and no
companion upload or public store rollout is required
+2 -2
View File
@@ -4,8 +4,8 @@ This guide covers practical upgrade steps for existing Pulse installs moving to
For the current v6 release candidate packet, see:
- `docs/releases/RELEASE_NOTES_v6.3.0-rc.2.md`
- `docs/releases/V6_CHANGELOG_v6.3.0-rc.2.md`
- `docs/releases/RELEASE_NOTES_v6.3.0-rc.3.md`
- `docs/releases/V6_CHANGELOG_v6.3.0-rc.3.md`
For the current stable v6 packet, see:
+1 -1
View File
@@ -6,7 +6,7 @@ set -euo pipefail
SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)"
DOCKER_IMAGE_REPO="${DOCKER_IMAGE_REPO:-rcourtman/pulse}"
CANONICAL_DEFAULT_PULSE_VERSION="6.3.0-rc.2"
CANONICAL_DEFAULT_PULSE_VERSION="6.3.0-rc.3"
resolve_default_pulse_version() {
if [ -n "${PULSE_IMAGE_VERSION:-}" ]; then