Poetry doesn't resolve to latest versions

[dmarinuswoodwing]

• I am on the latest Poetry version.

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

• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

• OS version and name: Linux

• Poetry version: 1.1.13

• Link of a Gist with the contents of your pyproject.toml file:
  https://gist.github.com/dmarinuswoodwing/135276f5bf976b6b338d35626319af89

Issue

When aws-sam-cli and moto added to pyproject.toml flask 1.1.2 gets installed.

aws-sam-cli depends on Flask (>=1.1.2,<1.2.0) so I'd expected poetry update to update to 1.1.4 but it doesn't for some reason.

when I add flask 1.1.4 to my pyproject.toml it does get upgraded.

moto has some overlapping indirect dependencies (jinja2, werkzeug, itsdangerous) with aws-sam-cli which might be at play.

[dimbleby]

Latest flask is not compatible with latest jinja2. Presumably the solver happens to take a path such that jinja2 'wins' and then flask is forced down.

If you care about latest flask then being explicit about that is the right thing to do.

Not a bug.

[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.