Use latest patch versions for testing and default version - #307

@jcfr The protected branch rules seem to specify that runs of Python 3.8.5 are required to pass prior to merging and same with python 3.9.9. The ci is being updated here in this PR to trigger runs of Python 3.8.12 and Python 3.9.10 instead, so updating of the required checks will likely need to be updated each time the latest version of the patch release to test is updated. This will be one update step to consider each time this happens.

All set. Required checks have been updated.

so updating of the required checks will likely need to be updated each time the latest version of the patch release to test is
updated. This will be one update step to consider each time this happens.

Reviewing https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions , I couldn't find a way to specify these outside of the project settings.

Something that could be listed in the maintainers guide ....

We could also remove the status check but I would rather being explicit and support the auto-merge feature .... https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request#about-auto-merge