Sourced fromfalcon's releases.

4.0.2

Falcon 4.0.2 is a minor point release (following the majorFalcon 4.0.0 release, and Falcon 4.0.1 bugfix) to fix some missed re-exports for type checkers. In addition, we have also included a couple of documentation improvements.

🐍Falcon 4.0.2 on PyPI

Fixed

Running Mypy on code that uses parts offalcon.testing would previously lead to errors like:

Name "falcon.testing.TestClient" is not defined

This has been fixed by explicitly exporting the names that are imported into thefalcon.testing namespace. (#2387)

Misc

The printable PDF version of our documentation was enabled on Read the Docs. (#2365)

4.0.1

Falcon 4.0.1 is a minor point release addressing a Python distribution issue inFalcon 4.0.0.

Fixed

Installing Falcon 4.0.0 unexpectedly copies many unintended directories from the source tree to the venv’ssite-packages. This issue has been rectified, and our CI has been extended with new tests (that verify what is actually installed from the distribution) to make sure this regression does not resurface. (#2384)

4.0.0

We are happy to presentFalcon 4.0, a new major version of the framework that brings a couple of commonly requested features including support for matching multiple path segments (usingPathConverter), and a fully typed codebase. (Please read more about typing in thenotes 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 forbinary wheels has been simplified usingcibuildwheel, 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 thelist 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 ourEuroPython 2024 Sprint. Some notable sprint contributions include CHIPS support, and a newWebSocket Tutorial, among others. In fact, according to thestatistics 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),andlet us know if you run into any issues!

Thank You!

4.0.0b4

Falcon4.0.0b4 is hopefully the final beta release of Falcon 4.0. Compared to4.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), andlet us know if you run into any issues!

... (truncated)

Sourced fromfalcon'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

Modifyfalcon/version.py if it has not been updated since the previousrelease. Examine the rendered changelog to determine the appropriate SEMVERfield to modify.

Note that we have droppedsetup.cfg altogether, so__version__ infalcon/version.py must contain thewhole version(including the previously separately managedtag_build), for instance:

# Development version__version__='4.0.0.dev1'Firstalphaversion='4.0.0a1'Releasecandidateversion='4.0.0rc1'Stablereleaseversion='4.0.0'

Update changelog filename inpyproject.toml to suit.

Update changelog and render towncrier fragments

If a changelog RST has not yet been created, add one underdocs/changes usingthe following template, and update the summary and changes to supportedplatforms to suit:

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

... (truncated)

• 4ac5ec6 chore: prepare Falcon 4.0.2 (in-tree) (#2392)
• ab2ce4c docs(FAQ): add entry for error tracebacks in ASGI apps (#2395)
• ca2e6d9 docs(typing): restructure typing docs into a separate chapter (#2401)
• 5c4406c docs(changes): add a newsfragment for#2365 (#2400)
• 8d03fb5 chore: publish sdist & pure-Python wheel without waiting for binaries (#2391)
• 6d7a45b fix: explicitly export the items in the falcon.testing namespace (#2388)
• 4d04e9b chore: incorporate Falcon 4.0.1 release notes (#2386)
• c5c1247 fix(dist): only detectfalcon* as packages (#2385)
• 1bfb819 Enabled pdf build format (#2371)
• f7189d7 chore: open 4.1.0.dev1 development
• Additional commits viewable incompare view

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)