Small issue with next version release detection

[ChurchCRMBugReport]

If the currently installed version is equal to the currently available version, then the logs indicate that the current version is actually the 0th release of the next minor version.

i.e. This issue is reported on 3.5.2, but the logs from the upgrade detection logic indicate 3.6.0 (which does not exist yet)

This will not negatively affect upgrade procedures, and is not an urgent bug to fix.

[2019-09-12 11:45:17] defaultLogger.DEBUG: Attempting to service query for release string 3.6.0 from GitHub release cache [] []
[2019-09-12 11:45:17] defaultLogger.DEBUG: Query for release string 3.6.0 did not match any GitHub releases.  Providing skeleton rel
ease object [] []
[2019-09-12 11:45:17] defaultLogger.INFO: The current release (3.5.2) is the highest release of it's Major/Minor combination. [] []
[2019-09-12 11:45:17] defaultLogger.INFO: Looking for releases in series: 3.6.0 [] []
[2019-09-12 11:45:17] defaultLogger.DEBUG: Determining the next-step release step for 3.6.0 [] []
[2019-09-12 11:45:17] defaultLogger.DEBUG: Evaluating next-step release eligibility based on 30 available releases  [] []

Collected Value Title	Data
Page Name	/v2/index.php
Screen Size	792x1372
Window Size	681x1372
Page Size	1919x1372
Platform Information	Linux CSHN001 4.4.0-159-generic #187-Ubuntu SMP Thu Aug 1 16:28:06 UTC 2019 x86_64
PHP Version	7.0.33-8+ubuntu16.04.1+deb.sury.org+1
SQL Version	5.7.27-0ubuntu0.16.04.1
ChurchCRM Version	3.5.2
Reporting Browser	Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.132 Safari/537.36
Prerequisite Status	All Prerequisites met
Integrity check status	{"status":"success"}
Apache Modules	core,mod_so,mod_watchdog,http_core,mod_log_config,mod_logio,mod_version,mod_unixd,mod_access_compat,mod_alias,mod_auth_basic,mod_authn_core,mod_authn_file,mod_authz_core,mod_authz_host,mod_authz_user,mod_autoindex,mod_cgi,mod_deflate,mod_dir,mod_env,mod_expires,mod_filter,mod_headers,mod_mime,mpm_itk,prefork,mod_negotiation,mod_php7,mod_rewrite,mod_setenvif,mod_socache_shmcb,mod_ssl,mod_status

[crossan007]

This can also be observed by attempting to load /UpgradeCRM.php?expertmode=1, and clicking the Fetch Update Files button, and observing the response:

Error making API Call to: /api/systemupgrade/downloadlatestrelease

Error text: Could not identify a suitable upgrade target release. Current software version: 3.6.0. Highest available release: 3.5.2

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 15 days with no activity.