spetz opened a new pull request, #4714:
URL: https://github.com/apache/iggy/pull/4714

   The Swift SDK had no release path. SwiftPM resolves packages only from
   a repository root with semver tags, the README pointed users at an
   apache/iggy-swift mirror that does not exist, foreign/swift carried no
   LICENSE or NOTICE, and its version was not on the edge scheme the
   other SDKs release from.
   
   A root Package.swift now publishes the Iggy library from
   foreign/swift, and the publish workflow tags releases as v<version>,
   the way it tags the Go module. Post-merge publishes X.Y.Z-edge.N
   snapshots, and a plain X.Y.Z is tagged only by a manual dispatch after
   the release vote. The publish step builds the root manifest without a
   lockfile before tagging, as a consumer would. Pre-merge fails when the
   root manifest drifts from foreign/swift/Package.swift, and
   bump-version.sh learns sdk-swift and regenerates the golden vectors
   that embed the version.
   
   A root manifest keeps one repository, one tag namespace for SwiftPM
   and the existing GITHUB_TOKEN tag push. A mirror repository would need
   a cross-repository credential, Infra authorization for automated
   pushes and recovery for publishes spanning two repositories, only to
   save consumers the first full clone.
   
   Relates to #4001


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to