Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump flit from 2.2.0 to 3.3.0 #655

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps flit from 2.2.0 to 3.3.0.

Changelog

Sourced from flit's changelog.

Release history

Version 3.3

  • PKG-INFO files in sdists are now generated the same way as METADATA in wheels, fixing some issues with sdists (410).
  • flit publish now sends SHA-256 hashes, fixing uploads to GitLab package repositories (416).
  • The [project] metadata table from 621 is now fully supported and documented <pyproject_toml_project>. Projects using this can now specify requires = ["flit_core >=3.2,<4"] in the [build-system] table.

Version 3.2

  • Experimental support for specifying metadata in a [project] table in pyproject.toml as specified by 621 (393). If you try using this, please specify requires = ["flit_core >=3.2.0,<3.3"] in the [build-system] table for now, in case it needs to change for the next release.
  • Fix writing METADATA file with multi-line information in certain fields such as Author (402).
  • Fix building wheel when a directory such as LICENSES appears in the project root directory (401).

Version 3.1

  • Update handling of names & version numbers in wheel filenames and .dist-info folders in line with changes in the specs (395).
  • Switch from the deprecated pytoml package to toml (378).
  • Fix specifying backend-path in pyproject.toml for flit-core (as a list instead of a string).

Version 3.0

Breaking changes:

  • Projects must now provide Flit with information in pyproject.toml files, not the older flit.ini format (338).
  • flit_core once again requires Python 3 (>=3.4). Packages that support Python 2 can still be built by flit_core 2.x, but can't rely on new features (342).
  • The deprecated flit installfrom command was removed (334). You can use pip install git+https://github.com/... instead.

Features and fixes:

  • Fix building sdists from a git repository with non-ASCII characters in filenames (346).
  • Fix identifying the version number when the code contains a subscript assignment before __version__ = (348).
  • Script entry points can now use a class method (359).
  • Set suitable permission bits on metadata files in wheels (256).
  • Fixed line endings in the RECORD file when installing on Windows (368).
  • Support for recording the source of local installations, as in 610 (335).
  • flit init will check for a README in the root of the project and automatically set it as description-file (337).
  • Pygments is not required for checking reStructuredText READMEs (357).
  • Packages where the version number can be recognised without executing their code don't need their dependencies installed to build, which should make them build faster (361).
  • Ensure the installed RECORD file is predictably ordered (366).

Version 2.3

  • New projects created with init_cmd now declare that they require flit_core >=2,<4 (328). Any projects using pyproject.toml (not flit.ini) should be compatible with flit 3.x.

... (truncated)

Commits
  • f6831de Version number -> 3.3.0
  • fb21769 Prepare release notes for 3.3
  • 82f1055 Merge pull request #423 from takluyver/doc-pep621
  • 3f5255a Document version constraints for flit_core build dependency
  • bc33d4d Flit now requires Python >=3.6
  • b44fac4 Update 'flit init' to use PEP 621 [project] table
  • 5f2d31d Add cross-reference to [tool.flit.module] section
  • c7c8ebc Fix warning about duplicate target
  • 58beed7 Start documenting PEP 621 support
  • bdfd972 Python 3.3 & 3.4 no longer supported for Flit CLI
  • Additional commits viewable in compare view

Dependabot compatibility score

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Bumps [flit](https://github.com/takluyver/flit) from 2.2.0 to 3.3.0.
- [Release notes](https://github.com/takluyver/flit/releases)
- [Changelog](https://github.com/takluyver/flit/blob/master/doc/history.rst)
- [Commits](pypa/flit@2.2.0...3.3.0)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Aug 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants