Merge release back into develop

[rstoneback]

Description

Addresses #(issue)

Merge release changes back into develop

Type of change

• Merge release changes back into develop

How Has This Been Tested?

Unit tests via GitHub

Checklist:

• Make sure you are merging into the develop (not master) branch
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• Add a note to CHANGELOG.md, summarizing the changes

[coveralls]

coverage: 99.465% (+99.5%) from 0.0%
when pulling e1bcd49 on main
into a6f4b0a on develop.