Keep easy update success state

[Teichoui]

Summary

Keeps the Easy Update button in its success state after a watched update completes successfully.

Why

The watched-update completion path was resetting the button back to the primary/blue state after a successful update, which made a completed update look less clearly successful.

Details

• Leaves the watched Easy Update button in the success state after successful watched updates.
• Keeps single-resource update reset behavior unchanged.
• Keeps failure behavior unchanged.

Validation

• python -m compileall -q src tests
• uv run --with pytest --with pytest-mock pytest
• git diff --check origin/main...HEAD

[Redbot]

that was on purpose! why forever green?

[Teichoui]

that was on purpose! why forever green?

when its not green you think it needs an update.

[Redbot]

what if that color reflected actual available updates? "redfetch check" was just added...

[Teichoui]

what if that color reflected actual available updates? "redfetch check" was just added...

if that is what you got working now that would be better.

[Redbot]

just an idea, no work yet.

in the tui, I think I'd like redfetch to report the results of "redfetch check" on launch in the terminal, and that can switch the color of the "easy update" button. Green if there are none.

[Teichoui]

Do you want it to only update on launch or on a set timer if redfetch is left open? And to check all plugins and what not that they have subs or on watch or just MQ build? Then they can bypass the download option and just start MQ?