You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When service version lower than latest are treated after latest is already treated this leads to versioning the latest in versioned and keep the incorrect version as latest.
example:
if a spec for version 2 is treated and later version 1 is treated the latest version will be the v1 and v2 get into the versions folder.
This pull request checks the sequence of versions and treats them in the correct order
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Related to SDK latest release event-catalog/sdk#44
Generator write a service version in versioned folder if under treatment current version in inferior of latest version
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
XaaXaaX
force-pushed
the
feat/verify-current-version-vs-latest
branch
3 times, most recently
from
Motivation
When service version lower than latest are treated after latest is already treated this leads to versioning the latest in versioned and keep the incorrect version as latest.
example:
if a spec for version 2 is treated and later version 1 is treated the latest version will be the v1 and v2 get into the versions folder.
This pull request checks the sequence of versions and treats them in the correct order