Skip to content

Python: Build(deps-dev): update flit-core requirement from <4.0,>=3.11 to >=3.11,<5.0 in /python in the flit group - #9839

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/python/flit-7deae4b9e4
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/python/flit-7deae4b9e4

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 29, 2026

Copy link
Copy Markdown
Contributor

Updates the requirements on flit-core to permit the latest version.
Updates flit-core to 4.1.0

Changelog

Sourced from flit-core's changelog.

Release history

Version 4.2

Flit :ref:now has a policy <llm_policy> against using AI/LLMs for development.

  • :ref:Sdist include & exclude patterns <pyproject_toml_sdist> are now matched regardless of Unicode normalisation form. This fixes a potential security issue, where a sensitive file may be published in an sdist even though it appears to match an exclusion rule. This may also depend on the filesystem, e.g. a rule that matches on Linux may not match on Mac, because Mac filesystems perform unicode normalisation.

    • If you have sensitive information in your project folder and you rely on include/exclude patterns to keep it out of sdists, it's still a good idea to check them carefully. A malicious contributor could still use other tricks, such as Unicode lookalike characters, to make a pattern that doesn't do what it appears to.
  • Flit will now refuse to build an sdist with symlinks that point outside of the project directory. This is a security issue for a consumer unpacking the sdist, and the consumer still needs to verify it, but this makes it harder to accidentally produce an sdist which consumers will reject.

  • Similarly, Flit will refuse to build wheels with symlinks pointing outside of the project directory, or using a README from outside the project directory. Either of these routes could previously have included files from the build machine into a wheel.

    • This change does not make it safe to build arbitrary untrusted packages with Flit; code from the package may still be executed. The aim is to make building more predictable, to reduce what needs to be manually verified. If you do not trust the source of a package, it is best to only attempt to build it in a secure sandbox with no access to sensitive information.
  • Allow environment markers to start with a parenthesised clause (:ghpull:836).

  • Text in [] brackets in requirements should only be name normalised if it is the name of an extra group (:ghpull:834).

  • Allow uploading to PyPI with a configured URL missing the trailing slash (:ghpull:829).

  • Fix flit install --symlink installing into a directory with spaces in the path (:ghpull:835).

  • Improved error messages for various cases, including hiding tracebacks in more cases where they are not informative (:ghpull:832, :ghpull:833, :ghpull:832, :ghpull:840, :ghpull:841)

Version 4.1

... (truncated)

Commits
  • 75b1c90 Merge pull request #826 from pypa/prepare-4.1
  • b5ad0d7 Add release note about PR #824
  • 9fb48c1 Bump version: 4.0.2 → 4.1.0
  • a4ea331 Prepare release notes for 4.1
  • 337c499 Merge pull request #824 from r3wretrhy/fix-win-cmd-crlf
  • 04cfa08 Merge pull request #825 from hxperl/docs-dynamic-fields
  • 33be607 doc: list all four fields accepted in project.dynamic
  • d538cb4 install: keep explicit CRLF in Windows .cmd wrappers
  • 3c92604 Merge pull request #809 from yangfan-yf-yf/fix/spdx-with-exceptions
  • 33a7a39 Clarify SPDX WITH version requirement and error message
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Updates the requirements on [flit-core](https://github.com/pypa/flit) to permit the latest version.

Updates `flit-core` to 4.1.0
- [Changelog](https://github.com/pypa/flit/blob/main/doc/history.rst)
- [Commits](pypa/flit@3.11.0...4.1.0)

---
updated-dependencies:
- dependency-name: flit-core
  dependency-version: 4.1.0
  dependency-type: direct:development
  dependency-group: flit
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Usage: [Issues, PRs], Target: dependencies in the project python Usage: [Issues, PRs], Target: Python labels Oct 29, 2026
Copilot AI balanced review requested due to automatic review settings October 29, 2026 14:42
@dependabot
dependabot Bot deployed to github-app-auth October 29, 2026 14:42 Active
@github-actions github-actions Bot changed the title Build(deps-dev): update flit-core requirement from <4.0,>=3.11 to >=3.11,<5.0 in /python in the flit group Python: Build(deps-dev): update flit-core requirement from <4.0,>=3.11 to >=3.11,<5.0 in /python in the flit group Oct 29, 2026
@dependabot
dependabot Bot deployed to github-app-auth October 29, 2026 14:42 Active

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

There are no active review issues for the change allowing Flit Core 4.x as a build dependency.

No open issues 🎉

What changed in this PR

This PR allows the Python NVIDIA integration package to use Flit Core 4.x for builds while retaining compatibility with versions starting at 3.11.

Changes:

  • Widens the flit-core build requirement from >=3.11,<4.0 to >=3.11,<5.0; no specific version is pinned.
  • Keeps the existing flit_core.buildapi build backend unchanged.
File Description
python/​packages/​nvidia/​pyproject.toml Allows Flit Core 4.x as a build dependency.

Review effort: Balanced

@eavanvalkenburg

Copy link
Copy Markdown
Member

Replicated the NVIDIA Flit Core build requirement update to >=3.11,<5.0 in the release-preparation branch: c040bbf . NVIDIA sdist and wheel builds pass. These changes are prepared on the branch only; they are not yet merged or released.

@dependabot @github

dependabot Bot commented on behalf of github Oct 30, 2026

Copy link
Copy Markdown
Contributor Author

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

@dependabot
dependabot Bot deleted the dependabot/uv/python/flit-7deae4b9e4 branch October 30, 2026 08:14

This branch was successfully deployed

1 active deployment
github-app-auth — ece5519e Deployed Oct 29, 2026 by dependabot[bot] via team_check #8016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Usage: [Issues, PRs], Target: dependencies in the project python Usage: [Issues, PRs], Target: Python

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants