Skip to content

Conversation

sureshkrishnan-v
Copy link

Description

This PR configures GoReleaser to sign release artifacts (checksums) using GPG.

  • Problem: Releases were not signed, which reduces trust for end users.
  • Resolution:
    • Added signs section to .goreleaser.yaml to sign checksums with GPG.
    • Updated .github/workflows/release.yml to import GPG key from GitHub Secrets and set required env variables (GPG_PRIVATE_KEY, GPG_PASSPHRASE, GPG_KEY_ID).
  • How to test:
    • Locally with goreleaser release --snapshot --clean --skip=publish using a test GPG key.
    • Verify signature with gpg --verify dist/checksums.txt.sig dist/checksums.txt.
  • No breaking changes.

Closes issue(s)

Resolve #3879

Checklist

  • I have tested this code locally
  • I have added unit test to cover this code (not needed for CI/config changes)
  • I have updated the documentation (README.md and /website/docs) if necessary
  • I have followed the contributing guide

Copy link

netlify bot commented Sep 16, 2025

Deploy Preview for go-feature-flag-doc-preview canceled.

Name Link
🔨 Latest commit b94403c
🔍 Latest deploy log https://app.netlify.com/projects/go-feature-flag-doc-preview/deploys/68e5faeb1b5d580008636e9e

Copy link

codecov bot commented Sep 16, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.92%. Comparing base (2a2ff14) to head (b94403c).
⚠️ Report is 114 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3909      +/-   ##
==========================================
- Coverage   83.97%   83.92%   -0.06%     
==========================================
  Files         136      137       +1     
  Lines        6797     6813      +16     
==========================================
+ Hits         5708     5718      +10     
- Misses        878      884       +6     
  Partials      211      211              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@sureshkrishnan-v sureshkrishnan-v changed the title (change) Configure GoReleaser to sign the releases ci: Configure GoReleaser to sign the releases Sep 16, 2025
@sureshkrishnan-v
Copy link
Author

@thomaspoignant Could you please review this PR and let me know if there’s anything wrong ?

@thomaspoignant
Copy link
Owner

@sureshkrishnan-v Thanks for your pull request, I will review it in the next few days as soon as I have some bandwidth.

Copy link
Owner

@thomaspoignant thomaspoignant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @sureshkrishnan-v thanks a lot for your pull request, this looks really great.

I've added a some comments, mainly about naming and also to use a github action in order to load the GPG key.
Also if you could have a look at the gemini review, it seems very valuable to add the --armor option.

If you have any question, don't hesitate to ask.

@thomaspoignant
Copy link
Owner

/gemini review

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly configures GoReleaser to sign release checksums using GPG, which is a great step towards improving the trust and integrity of the releases. The configuration uses environment variables for sensitive data and appropriate GPG flags for a CI environment. I have one suggestion to further improve the configuration by creating an ASCII-armored signature for better portability.

@thomaspoignant
Copy link
Owner

@thomaspoignant Could you please review this PR and let me know if there’s anything wrong ?

@sureshkrishnan-v I have reviewed the PR. Let me know if you need any help.

@sureshkrishnan-v
Copy link
Author

@thomaspoignant Could you please review this PR and let me know if there’s anything wrong ?

@sureshkrishnan-v I have reviewed the PR. Let me know if you need any help.

@thomaspoignant sure I will check with the comments and update the pr

@thomaspoignant
Copy link
Owner

@sureshkrishnan-v do you need help on this PR ?

Copy link

sonarqubecloud bot commented Oct 8, 2025

@sureshkrishnan-v
Copy link
Author

@thomaspoignant i have updated the required changes can you please check with my pr

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.

(change) Configure goreleaser to sign the releases
3 participants