Just an aside for decoding the version string: v3.3-65-g295ac49 means version 3.3 plus 65 commits to the code with a git identifying hash of 295ac49. (See attached, this is the FTLDNS branch, note the Latest commit that matches the hash.)
This is because we are based off of git for version control, but there's some discussion on changing that to another type of release. The (Latest: v3.3) is indicating the 'tag' of the git release. It's just cleaner to use tags, but in reality the v3.3 release is v3.3-0-g1e87850 (sometimes the -0- is missing, but that gets in to the internals of git and GitHub.)
No issue. All services appear to be running fine on original Raspberry Pi Model B after update.
However, as per the the topic heading, I was not able to determine whether there was an update available by looking at the web interface as suggested by Nero355.
You're right! It would just be a matter of passing though an extra flag. e.g pihole -up --check and then wrapping this section of code with something like:
if [[ ! ${1} == "--check" ]];then
if [[ "${FTL_update}" == true || "${core_update}" == true || "${web_update}" == true ]]; then
${PI_HOLE_FILES_DIR}/automated\ install/basic-install.sh --reconfigure --unattended || \
echo -e "${basicError}" && exit 1
fi
fi