Skip to content

Set up CI to audit for public dependency types #2925

@seanmonstar

Description

@seanmonstar

We want strict control over what types from dependencies we expose, and there is a tool that can help us check that in CI: cargo api-linter.

We should start by adding a new CI job to .github/workflows/CI.yml to use it. Any questions about what goes in the config file can be clarified here or in a PR.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-dependenciesArea: library dependencies.C-refactorCategory: refactor. This would improve the clarity of internal code.E-mediumEffort: medium. Some knowledge of how hyper internal works would be useful.

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions