Repository navigation
1.0.101: Check for updates always asks afresh
Check for updates always asks afresh
The sidebar badge asks the daemon a few seconds after every page load, and the daemon keeps that answer for an hour. A release published after that moment was invisible to Service → Check for updates until the hour passed, since the button read the same kept answer.
- Check for updates now skips the kept answer and asks GitHub at once; the fresh result replaces the kept one, so the sidebar badge follows.
- The badge and its six-hour timer are unchanged, and the daemon still asks GitHub at most once an hour for them.
Wiki: Service (Updates). Upgrade: msfe-ng upgrade, or the Service tab.