-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
poetry update --latest (w/ ignoring current pinning) #1944
Comments
I'd also prefer to have a more intuitive way of updating packages to the latest version. Right now, to update packages, I run this command, which seems to work fine (although it's not as clear as using a command called 'update'): |
@AndreCNF Thanks! It works like a charm! If that were documented somewhere, it'd be enough for me. |
I do notice that using this will change your version specification a bit. For example, if you have Flask = "1.1.1" and then do Flask = "^1.1.2" |
@Garrett-R That seems normal. What else were you expecting? |
I recently created a Python3 script to update all Poetry packages to their latest version while preserving extras and dependency groups. Check it out here |
|
Isn't it faster to delete the |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Issue
I've tried to search both documentation, issues and Web, but haven't found a solution for use case of "please update this package to newest version without reading current pinning in
pyproject.toml
". This is something I do quite often and so far I haven't found a clean way of doing it with Poetry.For example: I currently have
django = "^2.0.0"
in mypyproject.toml
but I'd like to upgrade that to the very latest version (3.0.2). I can of course change the pinning by hand topyproject.toml
but what if I want to upgrade my whole project to latest everything (every package)? What I'd like to is something likepoetry update --latest
Is there currently a way to do this without too much manual work (for one or many packages)?
The text was updated successfully, but these errors were encountered: