Skip to content

feat(issue-83): add cloudsmith repos gpg command group #390

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
BartoszBlizniak wants to merge 7 commits into from
Closed

feat(issue-83): add cloudsmith repos gpg command group #390

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
5bb95ce
feat(issue-83): add `cloudsmith repos gpg` command group
BartoszBlizniak Aug 12, 2026
cb8c3c8
fix(issue-83): harden repository GPG key upload
BartoszBlizniak Aug 13, 2026
df68bd4
test(issue-83): cover GPG mutation JSON output
BartoszBlizniak Aug 13, 2026
d03a122
test(issue-83): reset the thread-local CLI options between tests
BartoszBlizniak Aug 25, 2026
8f55b09
feat(issue-83): rework repos gpg confirmation, dry-run and error voice
BartoszBlizniak Aug 25, 2026
e9516de
fix(issue-83): detect stdin secret inputs by their raw value
BartoszBlizniak Aug 25, 2026
ec875e3
feat(issue-83): make the gpg dry runs check the key they would replace
BartoszBlizniak Aug 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.

## [Unreleased]

### Added

- Added `cloudsmith repos gpg` for managing the GPG key a repository signs its package indexes with. `get` shows the active key and its armored public block, `upload` installs a key you supply, and `regenerate` replaces the current key with a freshly generated Cloudsmith one. Key material and passphrases are only ever read from a file, stdin, or a hidden prompt, never from a command-line value, and `--debug` is refused on `upload` so the request body can't be logged. Both mutating subcommands accept `-n/--dry-run`, which checks the inputs and the key currently in place - naming the fingerprint that would be replaced - then stops before the request, so a mistyped repository or a stale credential fails there rather than on the real attempt. `regenerate` asks you to type `regenerate` to confirm - with no terminal attached it fails instead of blocking, so pass `-y/--yes` for unattended runs. There's no `delete` subcommand because the API has no way to remove a repository's key.

## [1.25.0] - 2026-08-24

### Added
Expand Down
Loading
Loading