Skip to content
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

Add support for "version ranges" in versioning #42

Open
bruno-f-cruz opened this issue Apr 13, 2023 · 1 comment
Open

Add support for "version ranges" in versioning #42

bruno-f-cruz opened this issue Apr 13, 2023 · 1 comment
Assignees
Labels
proposal Request for a new feature

Comments

@bruno-f-cruz
Copy link
Member

bruno-f-cruz commented Apr 13, 2023

The current device schema defines several target hardware, software, and firmware versions.
Since these schemas can target several versions simultaneously, we should add support to define version ranges.
The current suggestion is to adopt the specs followed by nuget.

Should use the https://www.nuget.org/packages/NuGet.Versioning package with NuGetVersion.Parse(string)

Or the range should be implemented in the already existing class HarpVersion

@bruno-f-cruz bruno-f-cruz added the proposal Request for a new feature label Apr 13, 2023
@bruno-f-cruz bruno-f-cruz changed the title Add support for Version ranges in semantic versioning Add support for "version ranges" in versioning Apr 13, 2023
@glopesdev
Copy link
Contributor

Related to harp-tech/protocol#44 and harp-tech/protocol#57

@glopesdev glopesdev modified the milestone: 0.2.0 Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal Request for a new feature
Projects
None yet
Development

No branches or pull requests

2 participants