Skip to content

[release-branch.go1.26] Ship .asc signature alongside .sig#2403

Open
gdams wants to merge 2 commits into
microsoft/release-branch.go1.26from
dev/gadams/sig1.26
Open

[release-branch.go1.26] Ship .asc signature alongside .sig#2403
gdams wants to merge 2 commits into
microsoft/release-branch.go1.26from
dev/gadams/sig1.26

Conversation

@gdams

@gdams gdams commented Jul 8, 2026

Copy link
Copy Markdown
Member

Backport of #2348

gdams and others added 2 commits July 8, 2026 13:00
Produce an .asc PGP signature file alongside the existing .sig for every
tar.gz archive. The .sig remains the default/primary extension; .asc is
shipped in parallel for compatibility with upstream Go tooling (e.g.
official Dockerfiles).

Fixes #181
Co-authored-by: Davis Goodin <dagood@users.noreply.github.com>
@gdams gdams requested a review from a team as a code owner July 8, 2026 12:01
Copilot AI review requested due to automatic review settings July 8, 2026 12:01

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Backports the signing tool change to ship an additional .asc signature file alongside the existing .sig for each signed archive, improving compatibility with upstream Go consumption tooling while keeping .sig as the primary signature output.

Changes:

  • Clarifies the in-code explanation of how .sig files are generated during signing.
  • Copies the generated .sig signature to the destination directory twice: once as .sig and once as .asc (same content).
Show a summary per file
File Description
eng/_util/cmd/sign/archive.go Produces an additional .asc signature artifact in the output directory alongside the existing .sig.

Review details

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Low

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.

2 participants