fix(pdm): ignore build requirements when update lock file

[huxuan]

Changes

Per discussion here, pdm does not lock build requirements in lock files, in this way, when we update lock file during dependency update, we should also ignore build requirements.

Context

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[rarkins]

Can these dependencies have "versions" in pyproject.toml? If so then we don't to skip them.

[huxuan]

Hi @rarkins, thanks for the attention.

Can these dependencies have "versions" in pyproject.toml? If so then we don't to skip them.

Yep, there do have versions for the build requirements and the version update actually works well. But the error happens when syncing the lock of the corresponding packages AFTER version update because pdm can not find them in the lock files. It is not a blocking error that breaks the version update, but more like a postprocessing error.

You can see the created pull request with errors here and the corresponding GitHub Actions log here

Sorry for the confusion, I should include the pull request and log earlier.

[renovate-release]

🎉 This PR is included in version 37.354.2 🎉

The release is available on:

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

Your semantic-release bot 📦🚀