vrr/Pulse
2
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-10-13 00:34:43 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 14

Keep server rollback guidance executable

Browse source
This commit is contained in:
pulse-triage[bot] 2026-08-29 10:15:45 +01:00
parent bf3d11729b
commit 505dcd571f
16 changed files with 93 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/UPGRADE_v6.md
View file

@ -260,7 +260,7 @@ Yes. Keep a rollback path available while you evaluate v6. The final release
on the v5 line is 5.1.36, so the stable rollback command is:
```bash
./scripts/install.sh --version v5.1.36
sudo /bin/update --version v5.1.36
```
### Why did my v5 install upgrade itself to v6?
@ -273,7 +273,7 @@ your data and configuration carry over; run through the Post-Upgrade
Checklist above to confirm everything still works. To return to v5, run:
```bash
./scripts/install.sh --version v5.1.36
sudo /bin/update --version v5.1.36
```
## Migration Notes (v6)

15
docs/release-control/v6/internal/subsystems/deployment-installability.md
View file

@ -100,6 +100,16 @@ upgrade must recover those values from both split and `--key=value` service
arguments and reproduce them in the generated systemd command without
discarding existing explicit disk exclusions.
Published exact-version install and rollback guidance must preserve the server
and Unified Agent installer boundary. Supported systemd and Proxmox LXC
deployments use the signed `/bin/update --version vX.Y.Z` server helper;
`/opt/pulse/scripts/install.sh` and release archives' `scripts/install.sh` are
Unified Agent installers and must never be presented as server rollback
commands. Docker guidance instead pins the target image and recreates the
container. The promotion resolver, manual release trigger, rendered release
body, current release packet, and shipped upgrade guide must agree on those
deployment-specific paths.
The accelerated exact-SHA release worker must preserve release-gate fidelity
under its own resource envelope. Bounded frontend static checks and integration
image preparation may overlap, but the full frontend test suite and the
@ -1740,6 +1750,11 @@ artifact-selection behaviour.
`frontend-modern/public/docs/UPGRADE_v6.md` byte-synchronized. The shipped
copy is part of every release packet, and `docsLinks.test.ts` must fail when
release preparation changes only one side.
16. Keep generated install and rollback instructions deployment-specific.
`scripts/installtests/build_release_assets_test.go` must reject a release
trigger, promotion resolver, rendered release body, current upgrade guide,
or current release packet that routes systemd/LXC rollback through the
Unified Agent installer, and must retain explicit Docker image guidance.
## Current State

2
docs/releases/RELEASE_NOTES_v6.4.0.md
View file

@ -21,4 +21,4 @@
- Existing configurations remain valid. Alert identity and history migrations run automatically, with no manual data migration required.
- Pulse Mobile iOS build 12 and Android versionCode 9 remain compatible. The new `alert_fired` push uses the existing `view_alert` action, so no companion mobile release is required.
- Windows Unified Agent binaries are not Authenticode-signed while SignPath remains unavailable and may show an Unknown Publisher warning. Verify downloads with the published checksums and detached signatures.
- The rollback target is stable `v6.3.2`. Use `./scripts/install.sh --version v6.3.2` if you need to return to the previous stable release.
- The rollback target is stable `v6.3.2`. On systemd and Proxmox LXC installs, use `sudo /bin/update --version v6.3.2` if you need to return to the previous stable release. For Docker Compose, pin the image to `rcourtman/pulse:6.3.2` and recreate the container.

2
docs/releases/V6_CHANGELOG_v6.4.0.md
View file

@ -60,7 +60,7 @@ This changelog describes the complete stable release train since `v6.3.2`.
- Promoted prerelease: `v6.4.0-rc.12`
- Runtime content cutoff: `18b22d1ebbfe542484652e419320fc7643a792f0`
- Rollback target: `v6.3.2`
- Rollback command: `./scripts/install.sh --version v6.3.2`
- Rollback command: `sudo /bin/update --version v6.3.2`
- Promotion path: owner-approved expedited exact-SHA stable cutoff from `main`
- Promotion decision: the release owner accepted a shortened soak to deliver bounded fixes for active monitoring correctness and collection-load harm. This is version-bound risk acceptance, not soak evidence or a standing exception.
- Windows signing decision: the standing SignPath-unavailable policy applies. Windows agents are not Authenticode-signed, may show an Unknown Publisher warning, and retain exact-SHA checksums, detached signatures, immutable-manifest verification, and published-digest verification.