aboutcode-org / aboutcode-org/univers

Properly handle the pre-release versions in VersionRange

未关闭
#130 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
3-next enhancement
主要语言
Python
星标
50
派生
29
PR 合并指标
30 天内没有已合并 PR

描述

The current univers `VersionRange` includes the pre-release versions. While this behavior is desirable when dealing with version ranges in a security advisory, it is not appropriate for the version range present in package manifests.

### Scenario:
Consider the following release versions for an npm package:
1.0.0, 1.2.0, 2.0.0-rc.1, 2.0.0, 2.1.0, and 3.0.0

#### Desired Behavior:

- When dealing with version ranges in a security advisory:
`2.0.0-rc.1` in `vers:npm/>=1.2.0|<2.0.0` => True

- When dealing with version ranges in manifest files:
`2.0.0-rc.1` in `vers:npm/>=1.2.0|<2.0.0` => False

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。