Skip to content

update cryptography pin #548

@kapilt

Description

@kapilt

afaics there isn't any reason why it should be limited to versions < 40, its generally considered a core ecosystem library, and for security reasons should generally not be locked to a specific revision set. afaics the only signficant change for folks using < 40 was those building from source, given almost all users are picking up via binary wheel, this seems irrelevant to the oci package usage.

relevant line from setup.py "cryptography>=3.2.1,<40.0.0",

Metadata

Metadata

Assignees

No one assigned

    Labels

    SDKIssue pertains to the SDK itself and not specific to any service

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions