Increase verboseness of poetry update cli command in documentation

[DhenPadilla]

• I have searched the issues of this repo and believe that this is not a duplicate.

Issue

I was getting quite frustrated with the poetry update <package_name> or poetry update <package_name>@latest command resulting in no-op. Since my pyproject.toml, the specified <package_name> had a version constraint of: ^0.28.0, and the latest version on PyPi was 1.3.4.

However, I finally decided to use poetry add <package_name>@^1.3.4 and this updated my desired package successfully, but this was not prompted via the documentation.

The docs for the poetry update command mentioned no-op for ~ version constraints, which lead me to (naively) believe that there should not be a no-op for ^0.28, although SemVer mentions this constraint as >=0.28, <1.0. I did not understand this beforehand, and was attempting to find constraints in the docs.
I think adding a quick reference to the documentation around SemVer/version constraints in the documentation for poetry update would help anyone new to SemVer.

[github-actions]

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.