Skip to content

chore(ci): validate non-EOL releases are signed with an "active" key - #43

Merged
aduh95 merged 1 commit into
mainfrom
add-ci-for-active-release-lines
Jul 15, 2025
Merged

chore(ci): validate non-EOL releases are signed with an "active" key#43
aduh95 merged 1 commit into
mainfrom
add-ci-for-active-release-lines

Conversation

@aduh95

@aduh95aduh95 commented Jul 9, 2025

Copy link
Copy Markdown
Contributor

The goal would be to recommend folks to use gpg-only-active-keys/pubring.kbx as the source of truth for verifying Node.js releases. For that, we'd need to ensure the keyring is always able to verify the supported versions, which this workflow should help us do that.

That means if a releaser needs to change the key listed as theirs, and that key was used to sign one the latest release, they can't do that until another release on that release line, or until said release line reaches EOL.

@aduh95
aduh95force-pushed the add-ci-for-active-release-lines branch from 9655346 to c8a2744CompareJuly 9, 2025 09:32
@aduh95
aduh95 requested a review from a teamJuly 11, 2025 18:52
@aduh95
aduh95 merged commit c8a2744 into mainJul 15, 2025
2 checks passed
@aduh95
aduh95 deleted the add-ci-for-active-release-lines branch July 15, 2025 06:58
Sign up for freeto 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.

2 participants

@aduh95@juanarbol