libpact_ffi.a files for all supported platforms are ridiculously large. LFS hosted on GitHub is out of the question for an OOS project. PactSwiftMockServer has already been set up to vend XCFramework package that strips down most of the unneeded runtime within the included libpact_ffi binaries.
Releasing a new version is tedious as it is currently done on a developer's machine and new XCFramework is pushed to the remote repository and tagged.
💬 Task Description
Create a GitHub action for release process that builds a new XCFramework, commits it into repository, tags the commit with version.
👩🔧 Technical Design Notes
refactor build_xcframework script to automate on CI without user interaction
put in failsafes (see previous point) avoiding unnecessarily blowing up the repo size
use a pactSwiftMockServer.version file?
check the version is bumped up compared to latest release version before continuing
surpher
commented
2 weeks ago
❕ Problem Statement
libpact_ffi.afiles for all supported platforms are ridiculously large. LFS hosted on GitHub is out of the question for an OOS project.PactSwiftMockServerhas already been set up to vendXCFrameworkpackage that strips down most of the unneeded runtime within the includedlibpact_ffibinaries.Releasing a new version is tedious as it is currently done on a developer's machine and new XCFramework is pushed to the remote repository and tagged.
💬 Task Description
Create a GitHub action for release process that builds a new XCFramework, commits it into repository, tags the commit with version.
👩🔧 Technical Design Notes
build_xcframeworkscript to automate on CI without user interactionpactSwiftMockServer.versionfile?🤝 Relationships