Cadwyn

Latest version: v4.4.3

Safety actively analyzes 688126 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 6 of 14

3.9.1

Fixed

* A broken link to docs in README.md

3.9.0

Added

* Support for getting openapi.json routes using API version headers instead of path query params

3.8.0

Added

* Discord status badge in README
* Logos to existing status badges in README
* An ability to specify multiple schemas when using `convert_request_to_next_version_for` and `convert_response_to_next_version_for` to be able to migrate multiple types of schemas using the same converter
* Redoc support

Removed

* Dependency from verselect. Now it is included as a part of Cadwyn

Fixed

* `h11._util.LocalProtocolError` when raising `HTTPException(status_code=500)`

3.7.1

Fixed

* Error message for changing path params of an endpoint in an incompatible manner which listed methods instead of path params

Changed

* Deprecated `cadwyn generate-code-for-versioned-packages` and added `cadwyn codegen` instead. It doesn't require `template_package` argument anymore and does not have the `ignore_coverage_for_latest_aliases` argument as we plan to remove this feature in the future. So it only requires `version_bundle`.

3.7.0

Changed

* Deprecated `cadwyn generate-code-for-versioned-packages` and added `cadwyn codegen` instead. It doesn't require `template_package` argument anymore and does not have the `ignore_coverage_for_latest_aliases` argument as we plan to remove this feature in the future. So it only requires `version_bundle`.

3.6.6

Fixed

* When a class-based dependency from **fastapi** was used (anything security related), FastAPI had hardcoded `isinstance` checks for it which it used to enrich swagger with functionality. But when the dependencies were wrapped into our function wrappers, these checks stopped passing, thus breaking this functionality in swagger. Now we ignore all dependencies that FastAPI creates. This also introduces a hard-to-solve bug: if fastapi's class-based security dependency was subclassed and then `__call__` was overriden with new dependencies that are versioned -- we will not migrate them from version to version. I hope this is an extremely rare use case though. In fact, such use case breaks Liskov Substitution Principle and doesn't make much sense because security classes already include `request` parameter which means that no extra dependencies or parameters are necessary.

Page 6 of 14

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.