fix(linux): Use ~ as pre-release separator for deb targets #7978
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.
Fixes: #7977
This PR translates the
-
pre-release separator (as mandated by the semver 2.0.0 spec, which is the format accepted bypackage.json
) to a~
, to match Debian's expectations on package versioning.See the below examples:
The reason why using
~
fixes this is because Debian orders the~
"lower" than the end-of-string character, and afaiu the reason such a special character was needed is exactly for use cases such as pre-releases.This also matches the fedora recommendations regarding packaging (which was first linked in this analysis, but this specific ordering issue was not caught due to the lack of explicit recommendations by Debian).