Skip to content

Migrate from actions/attest-build-provenance to actions/attest #575

Description

@james-garner-canonical

Per the release notes actions/attest-build-provenance is now a thin wrapper around actions/attest, and recommends using actions/attest directly for new projects. We might as well migrate and reduce our dependency chain.

Metadata

Metadata

Assignees

No one assigned

    Labels

    infraIssues with the repository infrastructure specifically.rainy daySmall items done in ~10% of each week's timeteam-charmlibs-maintainersMaintained by the canonical/charmlibs-maintainers team.

    Type

    Fields

    No fields configured for Task.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions