Skip to content

fix: handle breaking changes when current version is dev#308

Draft
KevinDeJong-TomTom wants to merge 3 commits intomasterfrom
fix/create-major-release-in-sdk-ver
Draft

fix: handle breaking changes when current version is dev#308
KevinDeJong-TomTom wants to merge 3 commits intomasterfrom
fix/create-major-release-in-sdk-ver

Conversation

@KevinDeJong-TomTom
Copy link
Collaborator

This commit restructures the SdkVer handling based on use-case mapping, simplifying the overall complexity of maintaining the flow.

This was needed to tackle the specific use case for failure of creating a new breaking change from a dev or rc version.

i.e. 1.0.0-dev001.SHA could not lead to 2.0.0-rc01 even
when specifying that this is a breaking change.

This commit restructures the SdkVer handling based on use-case
mapping, simplifying the overall complexity of maintaining the
flow.

This was needed to tackle the specific use case for failure of
creating a new breaking change from a `dev` or `rc` version.

i.e. `1.0.0-dev001.SHA` could not lead to `2.0.0-rc01` even
     when specifying that this is a breaking change.
);
}

/**
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file is unmodified from this point onwards...

@@ -0,0 +1,468 @@
/**
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file contains the SemVer bump functions, originally part of bump.ts - no changes to code have been applied

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant