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.

Sign up for GitHub

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

Jump to bottom

Support replacements with same version #33033

Open
rarkins opened this issue Dec 11, 2024 · 0 comments
Open

Support replacements with same version #33033

rarkins opened this issue Dec 11, 2024 · 0 comments
Labels
priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)

Comments

@rarkins
Copy link
Collaborator

rarkins commented Dec 11, 2024

Describe the proposed change(s).

Ref: #32844

We need the ability to replace package A with package B and maintain the same version. This is for cases where packages are being dual published but B is the preferred one.

We can keep a requirement on matchCurrentVersion but make replacementVersion be optional and equal currentValue (or currentVersion?) if unspecified.
@rarkins rarkins added type:feature Feature (new functionality) priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others labels Dec 11, 2024
@rarkins rarkins mentioned this issue Dec 11, 2024
Draft
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rarkins