fix(constraints): Pass along pre-release in all cases

[epage]

Fixes #1150

Pull Request Check List

This is just a reminder about the most common mistakes. Please make sure that you tick all appropriate boxes. But please read our contribution guide at least once, it will save you unnecessary review cycles!

• Added tests for changed code.
• Updated documentation for changed code. N/A

Note: If your Pull Request introduces a new feature or changes the current behavior, it should be based
on the develop branch. If it's a bug fix or only a documentation update, it should be based on the master branch.

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!

[epage]

I didn't see direct tests for this function so I was unsure what is the appropriate way of testing it.

EDIT: nm, found it and adding some

[epage]

Tests are now added

[epage]

@drunkwcodes could you clarify your thumbs down?

[drunkwcodes]

It's a non-issue because of the occurence of #1153.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[epage]

So while part of the problem was fixed in #1481, this problem still exists while this PR has been getting no attention from the maintainers. Do I bother resolving the conflicts or do I let the rudely applied bots close this?

[finswimmer]

Hey @epage,

So while part of the problem was fixed in #1481, this problem still exists [...]

could you please add some more details about what problem still exists?

Thanks a lot!

fin swimmer

[epage]

could you please add some more details about what problem still exists?

#1481 claimed to fix ~= but missed the case covered here: pre-release constraints.

[abn]

The relevant code in this PR has moved to poetry-core. This change, if still required, should be opened there.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.