[Feature]: From-Version Selection Rules

[Malcolmnixon]

Problem Statement

The BuildMark tool should enhance how it handles from-version selection.

Proposed Solution

Rules Summary

The rules differ from pre-release and release versions as follows:

• Pre-release: Pick the previous tag (release or pre-release) that isn't the same commit-hash
• Release: Pick the previous release tag

Pre-Release Example

For a pre-release let's consider:

• 1.1.2-rc.1 (git-hash a1b2c3d4)
• 1.1.2-beta.2 (git-hash a1b2c3d4)
• 1.1.2-beta.1 (git-hash 734713bc)

In this case when cutting 1.1.2-rc.1 it would identify that it's just a re-tag of 1.1.2-beta.2 and would skip that and instead pick a from-version of 1.1.2-beta.1

Release Example

For a release let's consider:

• 1.1.2
• 1.1.2-rc.1
• 1.1.2-beta.2
• 1.1.2-beta.1
• 1.1.1

In this case when cutting 1.1.2 it would jump back over the pre-release tags and pick a from-version of 1.1.1

In all cases if no previous version is identified then the history is built from the beginning of the repository.

Alternatives Considered

No response

Usage Examples

Benefits

More useful context information for build notes.

Priority

Medium - Would improve my workflow

Willingness to Contribute

Yes, I can submit a pull request

Additional Context

No response

Checklist

• I have searched existing issues to ensure this is not a duplicate
• I have provided a clear description of the feature
• I have explained why this feature would be useful