🎉 This PR is included in version 41.75.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 41.75.0

Your semantic-release bot 📦🚀

Hi @viceice ! If I may, I wanted to ask a question about this change. We currently use uv with renovatebot and do have various optional dependency-groups. After upgrading to this version, lock maintenance on uv.lock is no longer happening, although renovatebot continues to update the main dependencies section in pyproject.toml. PRs that were opened against dependencies in the groups were also auto-closed.

Is this the intended effect of this on uv and uv.lock? If it is and there is a migration guide, a quick link would be very appreciated! Thank you.

@viceice
me too. uv project is recognized as poetry even though there is no poetry.lock and there is a uv.lock.
I would love to have a guide on how to fix!

will look at it as fast as possible

As a temporary workaround, it looks like disabling the poetry manager entirely does solve this problem:

"poetry": {
    "enabled": false
  }

As a temporary workaround, it looks like disabling the poetry manager entirely does solve this problem:

"poetry": {
    "enabled": false
  }

Much appreciated, @viceice , @jonadaly ! Yes, we applied the enabled: false solution yesterday in the repo config and it worked liked a charm!

Before that, I was looking at supercedes.ts and realized that pep621's extractPackageFile function never populates the lockFiles attribute. Therefore, the logic in processSupersedesManagers will always make poetry win since it no longer (a) needs to be any poetry elements in pyproject.toml nor (b) checks for a presence of a poetry.lock file. It was sufficient that pep621 did not populate the lockFiles attribute for it to be overridden by poetry. I didn't look into how the bun / npm scenario was different.

Once I saw that, I arrived at the same conclusion @jonadaly did. But it's very nice to hear that it's a valid solution.

woking on a fix now, thanks @charlie-ang-collibra for the good analysation 🤗

• feat(pep621): return found lockfiles #37633
  this should fix it

it's not yet deployed to the hosted app