renovatebot/renovate

rez versioning: match range precision

Open

#12,476 opened on Nov 3, 2021

View on GitHub
 (4 comments) (0 reactions) (0 assignees)TypeScript (1,916 forks)batch import
help wantedpriority-4-lowversioning:rez

Repository metrics

Stars
 (14,066 stars)
PR merge metrics
 (Avg merge 2d 23h) (339 merged PRs in 30d)

Description

What would you like Renovate to be able to do?

Using rez package manager, I would like Renovate to be able to upgrade the version of dependencies while matching the current version precision of those dependencies.

For example, if foo-3.2.1 is the latest version available to update to, then: If the current version in the project is foo-1, then it should be updated to foo-3. If the current version in the project is foo-1.0 (or foo-1.x), then it should be updated to foo-3.2. If the current version in the project is foo-1.0.0 (or foo-1.x.y), then it should be updated to foo-3.2.1.

If you have any ideas on how this should be implemented, please tell us here.

Not yet.

Is this a feature you are interested in implementing yourself?

No

Contributor guide

Research direction
Implement version precision matching for rez packages in Renovate. Start by understanding how rez versioning works and how Renovate currently handles version pinning for other package managers. Then modify the rez versioning logic to preserve the precision of the existing version range when updating.
Tech stack
typescript
Domain
backenddevopstooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Gitnpmdependency management concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70