Skip to content

chore(deps): update dependency purpleclay/gpg-import to v0.10.0 - #252

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/purpleclay-gpg-import-0.x
Open

chore(deps): update dependency purpleclay/gpg-import to v0.10.0#252
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/purpleclay-gpg-import-0.x

Conversation

@renovate

@renovate renovate Bot commented Feb 5, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
purpleclay/gpg-import minor 0.5.00.10.0

Release Notes

purpleclay/gpg-import (purpleclay/gpg-import)

v0.10.0

Compare Source

0.10.0 - August 05, 2026

1 new feature • 2 bug fixes

Contributors

New Features

  • 27be7d3 support keys with zero or N subkeys and multiple uids (#​218) (@​purpleclay)

    parse_gpg_key_details hard-coded the colon-output shape sec -> fpr -> grp -> uid -> ssb -> fpr -> grp, breaking on sign-only keys (no subkey), multi-subkey keys (only the first of N ssb blocks was captured), and multi-uid keys (silently kept only the first). The fixed-shape parser was also fragile: take_until("ssb") scanned through uid content, so a uid containing the substring "ssb" derailed parsing entirely.

    Replace the fixed-shape nom parser with a hand-rolled, line-oriented one that dispatches on each record's own leading tag, immune to substrings inside field values. GpgPrivateKey now models uids: Vec and subkeys: Vec (0..N), each subkey carrying parsed sign/ encrypt/certify/authenticate capabilities. Downstream passphrase-preset, expiry-check, and --fingerprint-matching call sites are adapted to the new shape but stay behaviourally conservative (primary + first subkey only) where fuller N-subkey support is later, dependent work.

Bug Fixes

  • b50b55e adopt purpleclay/release-workflows for the release pipeline (#​236) (@​purpleclay)

    The in-repo build/package/publish jobs are replaced by the reusable release-rust.yml workflow, gaining clean-room builds, SLSA build provenance attestations, and a reviewer-gated release environment. The Rust toolchain is pinned to 1.97.1 to match flake.nix and avoid drift from the reusable workflow's floating stable default.

  • 151c5f4 parse import results via --status-file instead of localised stderr (#​216) (@​purpleclay)

    gpg::import_secret_key anchored on the literal stderr string "gpg: key ", which GnuPG gettext-translates on non-English locales — imports were silently reported as failed despite succeeding. Switch to gpg's machine-readable --status-file records (IMPORT_OK) and pin every spawned gpg/gpg-connect-agent command to LC_ALL=C with LANGUAGE unset, so any remaining human-oriented output stays deterministic.

Dependency Updates

Commit Update Contributors
8879949 update dependencies and migrate to Rust edition 2024 (#​229) @​purpleclay
b4e3c55 update github/codeql-action digest to f205ea1 (#​222) @​renovate[bot]
ad8e0dc update rust crate chrono to v0.4.45 (#​197) @​renovate[bot]
d1fc4a9 update softprops/action-gh-release action to v3.0.2 (#​219) @​renovate[bot]
92766de update rust crate insta to v1.48.0 (#​210) @​renovate[bot]
d2d5791 update github/codeql-action digest to 99df26d (#​209) @​renovate[bot]
544a754 update softprops/action-gh-release action to v3.0.1 (#​212) @​renovate[bot]
d6366f6 update actions/checkout action to v7 (#​211) @​renovate[bot]
fc9b543 update rust crate anyhow to v1.0.103 (#​213) @​renovate[bot]
febd288 update actions/checkout digest to df4cb1c (#​208) @​renovate[bot]
37816cc update cachix/install-nix-action digest to a49548c (#​214) @​renovate[bot]
3fabf71 update github/codeql-action digest to 87557b9 (#​193) @​renovate[bot]

Generated with release-note

v0.9.1

Compare Source

0.9.1 - June 01, 2026

Contributors

Dependency Updates

Generated with release-note

v0.9.0

Compare Source

0.9.0 - February 09, 2026

1 new feature

Contributors

New Features

  • 7378bf5 support reading GPG key from stdin or file (#​172) (@​purpleclay)

    Extend the --key flag to support alternative input methods:

    • Use - to read the key from stdin
    • Use @path to read the key from a file

    This enables piping keys directly from GPG export or reading from mounted secrets without storing keys in environment variables.

Generated with release-note

v0.8.0

Compare Source

0.8.0 - February 07, 2026

2 new features

Contributors

New Features

  • 10cad5c add flags to override git committer identity (#​168) (@​purpleclay)

    Add --git-committer-name and --git-committer-email flags to override the committer identity used in git config instead of using values from the GPG key.

    This is useful when the GPG key identity doesn't match the desired git committer or when using a shared/team GPG key with individual committer identities.

  • d4e084e add --git-global-config flag for global git signing configuration (#​167) (@​purpleclay)

    Allow users to apply git signing configuration globally instead of only against a local repository config. This does not require gpg-import to run within a git repository. Output messages now indicate whether local or global config was set.

Generated with release-note

v0.7.0

Compare Source

0.7.0 - February 06, 2026

2 new features

Contributors

New Features

  • 77e407c add --fingerprint flag to select specific key for signing (#​166) (@​purpleclay)

    Allow users to specify which key or subkey fingerprint to use for git commit signing via the --fingerprint flag or GPG_FINGERPRINT environment variable.

    When provided, the fingerprint is validated against the imported key's primary key and subkey fingerprints. If valid, it is used for the user.signingKey git config instead of the default primary key ID.

  • 144e2f0 support the import of ASCII armored GPG keys without the need for base64 encoding (#​165) (@​purpleclay)

    Auto-detect the input format when importing GPG keys:

    • If input starts with "-----BEGIN PGP", import as ASCII armored without decoding.
    • Otherwise, decode as base64 first.

    This allows users to pass GPG keys directly from gpg --armor --export-secret-key without needing to base64 encode them first. Base64 encoding remains supported for CI systems that don't handle multiline secrets well.

Dependency Updates

Generated with release-note

v0.6.0

Compare Source

0.6.0 - February 05, 2026

3 new features

Contributors

New Features

  • a65323e add --dry-run flag to simulate import without making changes (#​157) (@​purpleclay)

    Add GpgImport builder that encapsulates the import workflow and supports dry-run mode. When enabled, the import is simulated using:

    gpg --import-options show-only --with-colons --with-keygrip --import

    This allows the details of a key to be previewed without modifying the system.

  • ef8042c include error types for different gpg operations and validate through integration tests (#​156) (@​purpleclay)

  • 669878d replace unwrap calls with proper error propagation in the gpg module (#​148) (@​purpleclay)

Dependency Updates

Generated with release-note


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from purpleclay as a code owner February 5, 2026 08:53
@renovate
renovate Bot force-pushed the renovate/purpleclay-gpg-import-0.x branch from d7ddfeb to 3eff931 Compare February 6, 2026 10:01
@renovate renovate Bot changed the title chore(deps): update dependency purpleclay/gpg-import to v0.6.0 chore(deps): update dependency purpleclay/gpg-import to v0.7.0 Feb 6, 2026
@renovate
renovate Bot force-pushed the renovate/purpleclay-gpg-import-0.x branch from 3eff931 to 3542d38 Compare February 7, 2026 17:09
@renovate renovate Bot changed the title chore(deps): update dependency purpleclay/gpg-import to v0.7.0 chore(deps): update dependency purpleclay/gpg-import to v0.8.0 Feb 7, 2026
@renovate
renovate Bot force-pushed the renovate/purpleclay-gpg-import-0.x branch from 3542d38 to ad3ade0 Compare February 9, 2026 06:05
@renovate renovate Bot changed the title chore(deps): update dependency purpleclay/gpg-import to v0.8.0 chore(deps): update dependency purpleclay/gpg-import to v0.9.0 Feb 9, 2026
@renovate
renovate Bot force-pushed the renovate/purpleclay-gpg-import-0.x branch from ad3ade0 to d8a7006 Compare May 28, 2026 11:45
@renovate renovate Bot changed the title chore(deps): update dependency purpleclay/gpg-import to v0.9.0 chore(deps): update dependency purpleclay/gpg-import to v0.9.1 May 28, 2026
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate
renovate Bot force-pushed the renovate/purpleclay-gpg-import-0.x branch from d8a7006 to 79aa11f Compare August 5, 2026 05:24
@renovate renovate Bot changed the title chore(deps): update dependency purpleclay/gpg-import to v0.9.1 chore(deps): update dependency purpleclay/gpg-import to v0.10.0 Aug 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant