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)

• eeaf9e7 Merge pull request #839 from pypa/release/4.2
• 481d6c8 Update & rearrange release notes
• eba18d9 Merge pull request #841 from lprnmns/cli-invalid-version-error
• f291a9c Merge pull request #840 from lprnmns/check-requires-python-type
• 5d2a509 Show invalid version errors from the CLI without a traceback
• 0d1d5ed Check that requires-python is a string
• 9605622 Clarify about include/exclude rule tricks
• 840bd72 Finish sentence about rationale for symlink restriction
• 2f07598 Finish sentence in LLM policy
• ab319b2 Bump version: 4.1.0 → 4.2.0
• Additional commits viewable in compare view

Sourced from flit'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)

• eeaf9e7 Merge pull request #839 from pypa/release/4.2
• 481d6c8 Update & rearrange release notes
• eba18d9 Merge pull request #841 from lprnmns/cli-invalid-version-error
• f291a9c Merge pull request #840 from lprnmns/check-requires-python-type
• 5d2a509 Show invalid version errors from the CLI without a traceback
• 0d1d5ed Check that requires-python is a string
• 9605622 Clarify about include/exclude rule tricks
• 840bd72 Finish sentence about rationale for symlink restriction
• 2f07598 Finish sentence in LLM policy
• ab319b2 Bump version: 4.1.0 → 4.2.0
• Additional commits viewable in compare view