Remove pre-releases from release_notes

[rgee0]

Currently in draft as need to consider the effect in generation of release notes for a pre-release. As proposed, this would be cumulative over a number of pre-releases as prerelease is only consider when finding the previous release, so each pre-release will be considered against the previous full release.

Signed-off-by: Richard Gee richard@technologee.co.uk

Description

Initially the release notes were being generated from the current tagged release (n) and the n-1 release, irrespective of whether n-1 was a full release. This change causes getWorkingReleases() to ignore any previous releases where PreRelease is set to true. The processing beyond this determination will continue to consider all commits between the two identified points, resulting in a fuller set of changes for a full release where Pre-Releases have occurred in between.

Motivation and Context

• [x] I have raised an issue to propose this change (required)

Closes #184

How Has This Been Tested?

TBC

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [x] Feature Enhancement

Checklist:

• [x] My code follows the code style of this project.
• [x] My change requires a change to the documentation.
• [x] I have updated the documentation accordingly.
• [x] I've read the CONTRIBUTION guide
• [x] I have signed-off my commits with git commit -s
• [x] I have added tests to cover my changes.
• [x] All new and existing tests passed.