Skip to content

Please don't use a version range for hashbrown due to cargo resolver issues #420

@joshtriplett

Description

@joshtriplett

Using a version range for hashbrown causes packages depending on indexmap to experience oscillation between different versions of hashbrown, where updating can toggle between the latest versions on the 0.15 and 0.16 branch.

Please consider reverting the change to use a version range, to avoid this issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions