Skip to content

dependencies: drop PATCH version requirements #923

@xobs

Description

@xobs

I'm using a project that depends on espflash as a transitive dependency. They recently updated their version of espflash, and this has caused a dependency resolution in my project.

espflash requires a very specific minimum version -- 0.4.27. This has changed since the previous release of 0.4.22.

I can't see what new features espflash depends on, or why older versions are no longer supported.

If it's not required, espflash should not require exact patch versions so that it plays nicer with other projects and reduces its build footprint to avoid accidentally having multiple versions of a crate included in a build graph. This goes for all dependencies, and not just log.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions