Bump falcon from 3.1.3 to 4.0.0 in /src

[dependabot]

Bumps falcon from 3.1.3 to 4.0.0.

Release notes

Sourced from falcon's releases.

4.0.0

We are happy to present Falcon 4.0, a new major version of the framework that brings a couple of commonly requested features including support for matching multiple path segments (using PathConverter), and a fully typed codebase. (Please read more about typing in the notes on RtD.)

🐍 Falcon 4.0.0 on PyPI 📚 Changelog on RtD

The timeframe for Falcon 4.0 was challenging due to the need to balance our high standards with the CPython 3.13 timeline. We aimed to deliver the main development branch in this release, without resorting to another compatibility micro update (as we did with Falcon 3.1.1-3.1.3). Following community feedback, we also want to improve our overall release schedule by shipping smaller increments more often. To support this goal, we have made several tooling and testing improvements: the build process for binary wheels has been simplified using cibuildwheel, and our test suite now only requires pytest as a hard dependency. Additionally, you can run pytest against our tests from any directory. We hope that these changes should also benefit packaging Falcon in Linux distributions.

As with every SemVer major release, we have removed a number of previously deprecated functions, classes, compatibility shims, as well as made other potentially breaking changes that we could not risk in a minor version. If you have been paying attention the deprecation warnings from the 3.x series, the impact should be minimal, but please do take a look at the list of breaking changes on RtD.

This release would not have been possible without the numerous contributions from our community. This release alone comprises a number of pull requests submitted by a group of 30 talented individuals. What is more, we were particularly impressed by the high-quality discussions and code submissions during our EuroPython 2024 Sprint. Some notable sprint contributions include CHIPS support, and a new WebSocket Tutorial, among others. In fact, according to the statistics on GitHub, we are thrilled to report that the total number of Falcon contributors has now exceeded 200. We find it fascinating that our framework has become a collaborative effort involving so many individuals, and would like to thank everyone who has made this release possible!

4.0.0rc1

We are almost ready to release Falcon 4.0! :snake: 4.0.0rc1 on PyPI 📚 Changelog on RtD

We would greatly appreciate it if you could help us with the final round of testing on your apps (pip install falcon==4.0.0rc1), and let us know if you run into any issues!

Thank You!

4.0.0b4

Falcon 4.0.0b4 is hopefully the final beta release of Falcon 4.0. Compared to 4.0.0b3, we have made the timezone-aware datetime breaking changes more consistent, and documented the scope clearer.

🐍 4.0.0b4 on PyPI 📚 Changelog on RtD

Please test this beta release with your apps (pip install falcon==4.0.0b4), and let us know if you run into any issues!

Thank You!

4.0.0b3

This is the third beta release of Falcon 4.0; it is almost identical to 4.0.0b2 with the exception of one multipart form parsing bug that has been fixed (falconry/falcon#2364).

🐍 4.0.0b3 on PyPI 📚 Changelog on RtD

Please test this beta release with your apps (pip install falcon==4.0.0b3), and let us know if you run into any issues!

Thank You!

4.0.0b2

This is the second beta release of Falcon 4.0, where we made minor CI tweaks, and brought back the unintentionally removed, blocked resp.body property (it raises an instance of specialized AttributeError instead of a silent failure, making it much easier for the developer to track down this breaking change).

🐍 4.0.0b2 on PyPI 📚 Changelog on RtD

This release is otherwise largely identical to 4.0.0b1.

... (truncated)

Changelog

Sourced from falcon's changelog.

Release Manager's Guide

Release Process:

1. Bump version (including the suffix for pre-release, if applicable).
2. Update changelog and render towncrier fragments.
3. Release beta or rc.
4. Run benchmark and check for regressions.
5. Review and edit doc changes since the last release for clarity and consistency.
6. Publish final version and add a release note.
7. Run benchmark and update falconframework.org with latest numbers.
8. Announce the new version in Gitter channels and on the socials.
9. Improve this document.

Bump version

Modify falcon/version.py if it has not been updated since the previous release. Examine the rendered changelog to determine the appropriate SEMVER field to modify.

Note that we have dropped setup.cfg altogether, so __version__ in falcon/version.py must contain the whole version (including the previously separately managed tag_build), for instance:

# Development version
__version__ = '4.0.0.dev1'
First alpha
version = '4.0.0a1'
Release candidate
version = '4.0.0rc1'
Stable release
version = '4.0.0'

Update changelog filename in pyproject.toml to suit.

Update changelog and render towncrier fragments

If a changelog RST has not yet been created, add one under docs/changes using the following template, and update the summary and changes to supported platforms to suit:

Changelog for Falcon 4.0.1
==========================
Summary
</tr></table>

... (truncated)

Commits

• 5351220 docs(changes): prepare 4.0.0 stable (#2378)
• 61c1047 docs(changes): prepare Falcon 4.0.0rc1 (#2374)
• 9debc9e chore: prepare 4.0.0b4 (#2369)
• 872a45e docs(http_date_to_dt): describe the scope of timezone-aware date changes (#2368)
• 2556dbe chore: prepare 4.0.0b3 (#2367)
• db33c9c fix(multipart): do not require CRLF after the closing delimiter (#2366)
• 06fdf28 chore: prepare 4.0.0b2 (#2362)
• 8c7b5c0 refactor: restore AttributeRemovedError for resp.body (#2361)
• 25027b2 docs(4.0.0): add a forgotten word
• 9cbbb58 chore: prepare 4.0.0b1 release (#2359)
• 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 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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]

Superseded by #92.