Skip to content

fix(pkgrepo): support cross-organization release workflows - #63

Merged
jmgilman merged 2 commits into
mainfrom
fix/cross-org-signer-policy
Aug 22, 2026
Merged

fix(pkgrepo): support cross-organization release workflows#63
jmgilman merged 2 commits into
mainfrom
fix/cross-org-signer-policy

Conversation

@jmgilman

Copy link
Copy Markdown
Contributor

Summary

  • replace producer-relative package signer fields with explicit shared-workflow checksum and attestation identities
  • allow adopters to use meigma/release with organization-owned credentials across GitHub Releases, GHCR, Homebrew, Scoop, and native package repositories
  • dual-license the repository under Apache-2.0 OR MIT
  • replace the existing documentation with a focused Diátaxis set and update copyable release examples for every supported destination

Breaking change

Existing native package repository policies must replace checksum_workflow and attestation_workflow with checksum_identity and attestation_signer. Strict YAML decoding intentionally rejects the removed fields.

Verification

  • moon run root:check
  • nix flake check --all-systems --no-build
  • nix flake check
  • mise exec -- goreleaser check
  • mise exec -- goreleaser check examples/go-release/.goreleaser.yaml
  • go test ./... in examples/go-release
  • nix flake check --no-build in examples/nix-release-cli
  • validated Markdown links, anchors, fences, YAML parsing, and reusable-workflow interfaces

Package-repository policy derived Cosign and attestation identities from
the producer repository, which cannot describe a reusable workflow in
another repository. Require explicit immutable checksum identities and
signer workflows, dual-license the repository, and fail closed on
malformed trust values.
Consolidate the release documentation into a focused Diataxis set and update copyable examples for every supported destination.
@jmgilman
jmgilman merged commit 2d524ae into main Aug 22, 2026
3 checks passed
@jmgilman
jmgilman deleted the fix/cross-org-signer-policy branch August 22, 2026 15:31
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.

1 participant