Is your feature request related to a problem? Please describe.
Support for non sequential version numbering within the build process and checks
Describe the solution you'd like
Support for version numbering across multiple major/minor/patch threads at the same time. eg: if release go into 2.0 and a release needs to be updated in 1.2 then then product validator fails with
5:57:05 PM: Generating...
5:57:06 PM: Product Validator: Invalid releases '1.12' for nginx-ingress-controller.md, expecting release (released on 2022-10-19 00:00:00 +0000) to be before 2.0 (released on 2021-10-29 00:00:00 +0000).
Describe alternatives you've considered
Dropping support for release within data, have tried sorting by tag or date but see the same issue.
Is your feature request related to a problem? Please describe. Support for non sequential version numbering within the build process and checks
Describe the solution you'd like Support for version numbering across multiple major/minor/patch threads at the same time. eg: if release go into 2.0 and a release needs to be updated in 1.2 then then product validator fails with
5:57:05 PM: Generating... 5:57:06 PM: Product Validator: Invalid releases '1.12' for nginx-ingress-controller.md, expecting release (released on 2022-10-19 00:00:00 +0000) to be before 2.0 (released on 2021-10-29 00:00:00 +0000).
Describe alternatives you've considered Dropping support for release within data, have tried sorting by tag or date but see the same issue.
Additional context link to error on netlify https://app.netlify.com/sites/endoflife-date/deploys/672e50a742f0f30008b71db2