-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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.
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
DownloadPackage to support latest version #12334
DownloadPackage to support latest version #12334
Conversation
Very useful new feature. Right now have to do some hacking around to get it working with a 'latest' like behaviour. |
gently pinging reviewers @aasim @phil-hodgson @shubham90 @satbai @20shivangi |
Hi guys, do you expect this functionality to be reviewed soon? It will greatly help for a use-case I am developing. |
This is a very important functionality for my use case. Please make it so. |
gently pinging reviewers @aasim @phil-hodgson @shubham90 @satbai @20shivangi |
Hi Guys, has these been any progress on this? @aasim @phil-hodgson @shubham90 @satbai @20shivangi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks reasonable to me. @aasim could you also have a look, as you've worked on this task before. Sorry for the delay on reviewing this.
Can someone please resolve the remaining conflicts so the merge can be completed! This feature is fundamental for situations where npm is used to deploy custom build tools that are maintained. Not having to manually update ALL pipelines that are dependent on the latest version of a package would make my day so much nicer! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@evertonmc can you update the task version please?
@aasim Done |
Cool stuff, thanks for the quick resolution! I'm still new to this, when can I expect the change to take effect? |
When can we expect this change to be released? |
It's impossible to give an exact date, but as a rough estimate, you should start seeing the change within the first weeks of October. |
I assume this should be active now? I'm getting an error when I set version to "latest" on a universal package feed. |
It works on my pipeline! |
Thanks for the reply, but can I ask is it an option in the dropdown, or do you have to manually type it in? Because for me there is no option in the dropdown, and when I type in "latest" (as suggested by the tooltip) I get an error when it runs. |
Fixes #12333
I've added a 'latest version resolver' to select the current package at runtime.
latest