fix: use gpg passphrase secret

[bernardhalas]

• rename secrets for naming consistency reasons
• revert last commit, which was aiming to solve a problem; whereas the root cause was a wrongly named secret

Summary by CodeRabbit

• Chores
  • Updated release process configuration for GPG key management and passphrase handling to streamline automated signing during build pipelines.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Modified GPG signing configuration in the release pipeline by updating the passphrase secret reference from PASSPHRASE to GPG_PASSPHRASE in the GitHub Actions workflow and removing pinentry-mode loopback arguments from the goreleaser configuration.

Changes

Cohort / File(s)	Summary
GPG Signing Configuration .github/workflows/release.yml, .goreleaser.yml	Updated passphrase secret reference from PASSPHRASE to GPG_PASSPHRASE in GitHub Actions workflow. Removed --pinentry-mode loopback arguments from goreleaser signing configuration, altering how the GPG signing process handles passphrase prompts.

Possibly related PRs

• fix: add pinentry-mode loopback for GPG signing in CI #15: Directly related as it adds the --pinentry-mode loopback arguments to .goreleaser.yml that this PR removes, representing a reversal of that configuration change.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: renaming the GPG passphrase secret from PASSPHRASE to GPG_PASSPHRASE for consistency.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}