-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improved calculating pre-release versions that start with the same base name #1064
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
57be9b8
Exported `getDateIdentifier()` from the `ckeditor5-dev-release-tools`…
psmyrek 06114d0
Improved mocked data in test.
psmyrek 20be140
Tests.
psmyrek dc597e1
Tests.
psmyrek b90cd72
Match the dot in the optional sequence number literally.
psmyrek File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a random idea, but maybe we should separate all bits that are important to us by
.
instead of a mix of.
and-
?Given this example:
This version number consists of:
However, according to spec, each identifier in the pre-release portion (after first
-
) should be dot-separated, so the correct version should be:This version number consists of:
With this approach, we could use
semver
(which we already have) to parse version numbers instead of using Regexp.If this is the only place we do it, then it shouldn't be an issue, but if we have more such places, then relying on official npm tooling would be nice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, due to the fact we are separating
nightly-YYYYMMDD
with-
instead of.
, we can't usesemver.prerelease()
to parse the version, so currently we are doing it manually with regexp.So question is do we accept to change the versioning for all nightly releases:
0.0.0-nightly-YYYYMMDD.X
->0.0.0-nightly.YYYYMMDD.X
0.0.0-nightly-next-YYYYMMDD.X
->0.0.0-nightly.next.YYYYMMDD.X
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am fine with it, but I wonder if it's a breaking change. Or, whether it should be marked as.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After discussing this within the team, we decided not to change the nightly versioning format.