fix: use release-plz bot signing identity #113
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Slipstream/emc!113
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/release-plz-bot-signing-identity"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Rationale
The RELEASE_SIGNING_KEY belongs to the release-plz-bot Forgejo account. The previous default identity used John Wilger, so Forgejo still rejected the signed release PR commit as unverified. Aligning the commit identity with the signing-key owner should satisfy branch protection.
Verification
This PR updates the release workflow to use the release-plz-bot identity for signing commits, aligning the commit identity with the signing key owner. This change should resolve issues with unverified commits due to mismatched identities.
Walkthrough
release-plz-botto match the signing key owner, ensuring that commits are verified correctly.release-plz-bot, clarifying the relationship between the signing key and the commit identity.LLM usage and cost
Estimated total USD: $0.009844 via https://api.openai.com and https://api.openai.com
🟡 Warning: Ensure that the email domain
noreply.git.johnwilger.comis correctly configured to avoid potential issues with email verification or delivery.Handled auto_review warning on noreply.git.johnwilger.com: the release commit email now matches the Forgejo account email returned by /users/release-plz-bot, release-plz-bot@noreply.git.johnwilger.com. This is used for Forgejo commit verification, not external email delivery.