Publish independently versioned Swift packages with shared checks and release evidence.
Overview · Quick look · Install · Usage · Requirements · Documentation · Contributing · License
Connect a package’s own check command and compiler matrix to reusable validation and publication workflows. Pull requests report public API changes for maintainer review, and releases attach validation results and a scoped API snapshot; the workflow reference explains caller inputs and collection gaps.
Call the shared validation workflow from a package:
jobs:
validate:
uses: swift-library/.github/.github/workflows/swift-package-ci.yml@9aa78ca8d6346242460006178b9808114beee9f8Follow workflow integration to add package-owned release configuration and callers pinned to full commit SHAs. Start a new repository with the package template.
Keep source, versions, compatibility, and validation commands in each package. Use VERSIONING.md for release decisions, MAINTENANCE.md for contribution and GitHub governance, and DESIGN.md for the shared presentation system.
- GitHub Actions for reusable workflow callers
- Python, actionlint, and GitHub CLI for local standards checks
- The compiler, SDK, and platform declarations owned by each consuming package
Read CONTRIBUTING.md and run Scripts/check before submitting a pull request. Follow the code of conduct and support guide.
Apache-2.0 WITH Swift-exception. Each package retains its own source and dependency notices.