Skip to content

test: update older releases to the build in CI - #37

Merged
Variiuz merged 3 commits into
mainfrom
test/update-from-older-releases
Nov 10, 2026
Merged

Variiuz merged 3 commits into
mainfrom
test/update-from-older-releases

Conversation

@Variiuz

@Variiuz Variiuz commented Nov 10, 2026

Copy link
Copy Markdown
Owner

Nothing tested that a host on an older release can update to a new build: the old binary's mayfly update and the new binary's mayfly install run together for the first time on a real host.

tests/update.sh <dist> installs a real older release from GitHub into a stub root (MAYFLY_* paths, stubbed qm/pvesh/pvesm/systemctl/apt-get), serves the packaged build as the latest release from a local server, and runs the old binary's mayfly update. It checks:

  • the new version is installed and its mayfly.sh is in the share directory
  • pool.env, slots.conf, env/, hooks.d and profiles/ are byte-for-byte unchanged
  • all five units are present, and the old version is saved in previous/
  • update --check then reports up to date
  • update --rollback restores the old version, the config is still unchanged, and update --auto skips the rolled-back release

CI runs it after packaging, from the previous release and from 0.4.1 (the first with mayfly update). Locally: 14/14 from 0.8.0 and 0.4.1 to 0.8.1.

Notes: none (tests only).


Generated by Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GGBbe8FgqqUCF5fNkd9Ndi
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GGBbe8FgqqUCF5fNkd9Ndi
@Variiuz
Variiuz merged commit 1ea8f6e into main Nov 10, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants