plan: report a changed generation id as a change #9

Merged

chad merged 1 commit from plan/changes-on-generation-id into master

2026-10-15 14:44:50 -04:00

glen commented

2026-10-15 14:41:29 -04:00

Collaborator

Found while declaring an already-installed flatpak (cn: Slack desktop). The declaration changed, so apply would realize a new generation, but nothing needed installing, so plan printed "no changes — already at the declared state" and --json said changes: false. That would also hide the edit from the daily drift check.

changes is now also true when the planned generation id differs from the current one.

Verified on think: the Slack-declaring profile now shows generation: 607a31f45def -> ca6cdec35b96, and the live unchanged profile still reports no changes. cargo test --workspace: 135 pass.

Non-urgent: v0.4.0 behaves correctly apart from this misreport. It can ride the next release.

Found while declaring an already-installed flatpak (cn: Slack desktop). The declaration changed, so `apply` would realize a **new generation**, but nothing needed installing, so `plan` printed "no changes — already at the declared state" and `--json` said `changes: false`. That would also hide the edit from the daily drift check. `changes` is now also true when the planned generation id differs from the current one. **Verified on think:** the Slack-declaring profile now shows `generation: 607a31f45def -> ca6cdec35b96`, and the live unchanged profile still reports `no changes`. `cargo test --workspace`: 135 pass. Non-urgent: v0.4.0 behaves correctly apart from this misreport. It can ride the next release.

glen added 1 commit

2026-10-15 14:41:29 -04:00

plan: report a changed generation id as a change (declaration-only edits) a56a3a7247