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 摘要。