Skip to content

Sign plugin releases with PGP #341

@vlsi

Description

@vlsi

Currently, the plugin is not signed, so dependency verification has to use checksums.

See:


Note: if you release with GitHub Actions workflow, then you can generate PGP key and keep it in GitHub secrets.
See: https://github.com/vlsi/provision-release-pgp-key

The idea is that you add a workflow to trigger key provisioning like in https://github.com/pgjdbc/pgjdbc/blob/ee09a2f3bf2cb9031e2e325503281f2c1b2d4761/.github/workflows/pgp-key-maintenance.yaml
Then you manually trigger it and it generates and stores the key to GitHub variables. The same workflow can extends the key lifetime.

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