Mathieu Kniewallner

@neersighted I'd like to see that backported to `1.2` branch as well, unless you think that only the hook fixes (and not the new hook) should be backported to `1.2`....

> I'm not 100% sure on this just yet -- or rather I'm not sure on the future of pre-commit hooks in this repo given that upstream is incompatible with...

I don't have all the background on past decisions, but reading through https://python-poetry.org/docs/cli/#version and the code, it looks like this is the expected behaviour (albeit a probably confusing one for...

I may not have enough knowledge to be 100% sure of that, but I am also under the assumption that poetry-core is never doing any write operations on TOML files....

Side note first: Please be respectful of people that take some of their time to help you, even if in the end it doesn't fix your issue. Remember that people...

This should probably be great to backport to 1.2 too, since there's a great chance that dependencies will get updated there too.

> I'd like to take a different approach with this as a pre-req for the main workflow. That being said, that would be part of the CI rework I'd like...

While I don't have data to back that, I would tend to agree with @dimbleby, as I believe that the main usage of `secondary` is to declare private dependencies, or...

> What about an `isolated = true` option for sources that are `secondary = true`? This would **only** use the source for the packages that explicitly use that source and...

Does anyone of you still reproduce the issue on version [1.1.13](https://github.com/python-poetry/poetry/releases/tag/1.1.13) and/or [1.2.0b1](https://github.com/python-poetry/poetry/releases/tag/1.2.0b1)?