The release includes a fix for stale local worker reuse across app versions, so upgraded clients stop carrying over obsolete local worker state from earlier versions.
Scattered source updates, isolated context, and manual follow-up across multiple feeds.
Adds a lifecycle fix so local workers are not reused across app-version boundaries, preventing stale in-memory/runtime state from being applied after an upgrade.
Operators and developers upgrading Opencove are less likely to hit inconsistent runs after update, because local workers are prevented from reusing outdated state and are treated as fresh units for the new version. This appears to improve upgrade stability by isolating worker state transitions, so watch for first-start latency on update and verify that no stale worker IDs or cached sessions reappear in logs after repeated upgrades.
Operators and developers upgrading Opencove are less likely to hit inconsistent runs after update, because local workers are prevented from reusing outdated state and are treated as fresh units for the new version. This appears to improve upgrade stability by isolating worker state transitions, so watch for first-start latency on update and verify that no stale worker IDs or cached sessions reappear in logs after repeated upgrades.