Link to issue number:

Fixes #17800
Follow-up of #17310

Summary of the issue:

The changes introduced in PR #17310 had a bug. If the version being checked for an update is the latest for the given versionType, the server returns an empty response. This caused an error because the required keys for a valid update response were missing.

Description of user facing changes

With the update mirror validation in place, checking for updates while running the latest version will now correctly result in the standard message indicating that no update is available.

Description of development approach

1. In the checkForUpdate function, check whether the response is an empty string. If so, simply return None, indicating that no updates are available.

Testing strategy:

1. Implement the fix.
2. Modify versionInfo.py and buildVersion.py to simulate an alpha version.
3. Run NVDA and check for updates via Help → Check for Updates.
4. Ensure that the message is correct and confirms that no updates are available.
5. Revert changes to versionInfo.py and buildVersion.py to restore the generated source version.
6. Run NVDA again and ensure that the update check is still valid, confirming that no updates are available for the source version.

Known issues with pull request:

Code Review Checklist:

• Documentation:
  • Change log entry
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English
• API is compatible with existing add-ons.
• Security precautions taken.

@coderabbitai summary