fix: do not jump unstable versions implicitly
If the current value is already unstable then we presume the user is happy to take newer unstable versions. However we should not presume that they want to keep jumping versions if so and instead would prefer to stabilise. Discussed in #2258 but does not close it
Showing
- lib/workers/repository/process/lookup/filter.js 13 additions, 4 deletionslib/workers/repository/process/lookup/filter.js
- test/_fixtures/npm/typescript.json 1 addition, 1 deletiontest/_fixtures/npm/typescript.json
- test/workers/repository/process/lookup/__snapshots__/index.spec.js.snap 22 additions, 23 deletions...epository/process/lookup/__snapshots__/index.spec.js.snap
- test/workers/repository/process/lookup/index.spec.js 18 additions, 17 deletionstest/workers/repository/process/lookup/index.spec.js
Loading
Please register or sign in to comment