Thanks for the example, I think I understand what is happening. You are using automatic release creation and you would like a release to be created whenever a “newer” package (by date) is pushed to the package feed.
As you have observed, automatic release creation will create a release only when a new package by version is pushed to the package feed. The metadata part of the version is compared using a string comparison, so you are not getting the result you want (6 appears before 12 for example).
Would it be possible to slightly alter your versioning scheme to move the metadata into the pre-release part of the version? The version comparison considers the pre-release version more intelligently than the metadata. For example,
1.0.0-beta.6 would be considered older than
1.0.0-beta.12 and I think you would end up with the result you want.
Please let me know if this helps.