vrr/Pulse
2
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-07-09 16:00:59 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 7

Explain the pre-5.1.29 auto-update jump to v6 in the upgrade guide

Browse source 
v5 installs on 5.1.28 and older have no release-line pin, so with
auto-update enabled they silently in-place upgrade to the newest stable
GitHub release, which is now v6. Add an FAQ entry for the operator who
lands on v6 without asking, and point the rollback path at 5.1.36, the
final v5 release (was 5.1.35).
This commit is contained in:
rcourtman 2026-07-08 22:56:57 +01:00
parent ef25600270
commit 8222f132a8
1 changed files with 16 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

19
docs/UPGRADE_v6.md
View file

@ -132,11 +132,24 @@ servers.
### Can I keep Pulse v5 stable while I test Pulse v6?
Yes. Keep a rollback path available while you evaluate v6. For the v6.0.0 GA
cutover, the stable rollback command is:
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.35
./scripts/install.sh --version v5.1.36
```
### Why did my v5 install upgrade itself to v6?
Pulse 5.1.29 and later pin the built-in updater to the 5.1.x line and never
offer v6, so upgrading from those versions is always a manual step. Pulse
5.1.28 and older have no such pin: installs with auto-update enabled follow
the newest stable GitHub release, which is now v6. If that happened to you,
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
```
## Migration Notes (v6)