Dropped support for older Poetry versions should be a major version update

[rene-gentzen-mittelstand-ai]

Hey mate, we install the plugin via poetry self add poetry-plugin-bundle in a lot of Dockerfiles. This does no longer work since we are sticking to Poetry 1.8.x for now.
poetry self add "poetry-plugin-bundle@^1.0.0" fixes the installation error but for some reason poetry will try to install version 1.6.0 and just fail due to the poetry version constraints if the version specifier is ommitted.
In my opinion something as huge as dropping support for the longterm default version of poetry a mere six weeks after its release should lead to poetry-plugin-bundle 2.0.0.

That being said, thanks for the awesome plugin!

[radoering]

The actual issue is python-poetry/poetry#707. If you install Poetry and the plugin via pipx (see https://python-poetry.org/docs/#installing-with-pipx and https://python-poetry.org/docs/plugins/#using-plugins), a suitable version of the plugin should be chosen.

[rene-gentzen-mittelstand-ai]

I see, thanks for digging that up! It made the root of the issue clearer for me.

I stand by my opinion (and at least one person agrees) that only being compatible with the new version of the tool that you are a plugin of is the most breaking change you can make and should lead to a major version upgrade.
But if you disagree feel free to close this issue. I don't want to bloat the issues list with stuff that is more philosophical than practical.