carvel-dev
Package consumers should have the option to install the latest available version of a package without it being auto-updated
Describe the problem/challenge you have When installing a package, the consumers can either provide a specific version to install OR they can provide some constraints which will keep the package updated to the latest version satisfied by the provided constraints.
There is another use case where a consumer might want to install the latest available version of the package however does NOT want it to update when a new version is available. So, for example, if there are three versions of a package available (v1.0, v2.0, and v3.0), they would like to install the latest that is v3.0 but NOT update it automatically when a new version (v4.0) is available.
Describe the solution you'd like [A clear and concise description of what you want to happen. If applicable a visual representation of the UX.]
Anything else you would like to add: [Additional information that will assist in solving the issue.]
Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible" 👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.
This one feels weird, why not just provide the constraint? I guess a lot of the context of this one might be lost, so I am going to leave it open for archive sake, but I don't see this being worked on for the foreseeable future
