-
Notifications
You must be signed in to change notification settings - Fork 12
chore: add semver spec for build metadata #127
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
Open
daveleek
wants to merge
11
commits into
main
Choose a base branch
from
chore/semver-metadata-spec
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
4f292c4
chore: add semver spec for build metadata
daveleek b6fa2ae
Update specifications/14-constraint-semver-operators.json
daveleek 48d4384
Update specifications/14-constraint-semver-operators.json
daveleek c1ea7d8
Update specifications/14-constraint-semver-operators.json
daveleek 85a8e4c
Update specifications/14-constraint-semver-operators.json
daveleek bf82e00
Update specifications/14-constraint-semver-operators.json
daveleek acbc58d
Update specifications/14-constraint-semver-operators.json
daveleek 38897af
Update specifications/14-constraint-semver-operators.json
daveleek 358cb5e
Update specifications/14-constraint-semver-operators.json
daveleek 3e7e3c2
Update specifications/14-constraint-semver-operators.json
daveleek 7e71e5b
Update specifications/14-constraint-semver-operators.json
daveleek 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 hidden or 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
Oops, something went wrong.
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.
I understand SemVer 2.0.0 defines precedence (you should ignore metadata for precedence comparison), but it doesn't say anything about equality.
This gives us:
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.
Good point. We do only want the SemVer precedence comparison then is my understanding here? @sighphyre
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.
@gastonfournier with "compare(1.2.2+foo, 1.2.2) == 0" are you suggesting that we do not take metadata into consideration when establishing equality?
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 think this is horribly debatable but I agree with Gaston here: 1.1.1+foo == 1.1.1
For no other reason than if you force an exact match here then you can get into a weird place where two semantic versions do not satisfy any of A >= B, A > B, A == B, A < B or A <=B... which... is weird
No idea how SDKs are going to handle this, so should be funnn to roll this out