Closed konrad-jamrozik closed 7 months ago
This is a follow-up to:
The PR 664 introduced a bug where versions were incorrect and couldn't be published, e.g.:
2024-03-08T18:46:10.4580795Z npm ERR! Invalid version: "2.0.1.1" ... 2024-03-08T18:46:10.4581885Z @microsoft.azure/openapi-validator-rulesets@2.0.1.1 failed.
Basically I forgot to add -beta so it would be 2.0.1-beta.1. But now I just got rid of the increments altogether.
-beta
2.0.1-beta.1
Related package: https://www.npmjs.com/package/@microsoft.azure/openapi-validator-rulesets?activeTab=versions and release: https://dev.azure.com/azure-sdk/internal/_releaseProgress?_a=release-environment-logs&releaseId=24491&environmentId=30146&jobTimelineRecordIdToSelect=f50f743f-9194-5eb0-5ce7-c6df31e790c2&selectTaskWithIndex=5#
This is a follow-up to:
The PR 664 introduced a bug where versions were incorrect and couldn't be published, e.g.:
Basically I forgot to add
-betaso it would be2.0.1-beta.1. But now I just got rid of the increments altogether.Related package: https://www.npmjs.com/package/@microsoft.azure/openapi-validator-rulesets?activeTab=versions and release: https://dev.azure.com/azure-sdk/internal/_releaseProgress?_a=release-environment-logs&releaseId=24491&environmentId=30146&jobTimelineRecordIdToSelect=f50f743f-9194-5eb0-5ce7-c6df31e790c2&selectTaskWithIndex=5#