Skip to content

chore: use release-keys keyring for gpg fingerprints#2459

Open
nschonni wants to merge 1 commit intonodejs:mainfrom
nschonni:parse-keyring-on-update
Open

chore: use release-keys keyring for gpg fingerprints#2459
nschonni wants to merge 1 commit intonodejs:mainfrom
nschonni:parse-keyring-on-update

Conversation

@nschonni
Copy link
Copy Markdown
Member

Description

This doesn't change to go away from the keyservers like in #2415, but points to the upstream source, and removes the need for PRs here when onboarding new Releasers.

Motivation and Context

Testing Details

Example Output(if appropriate)

Types of changes

  • Documentation
  • Version change (Update, remove or add more Node.js versions)
  • Variant change (Update, remove or add more variants, or versions of variants)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Other (none of the above)

Checklist

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING.md document.
  • All new and existing tests passed.

@nschonni
Copy link
Copy Markdown
Member Author

@aduh95 this doesn't replace your PR, but was what I was trying to explain in the thread. If your approach doesn't get accepted by the Docker Hub people, this at least streamlines the Releaser onboarding and revoking of old keys process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant