{"id":14195,"date":"2022-07-15T07:00:44","date_gmt":"2022-07-15T05:00:44","guid":{"rendered":"https:\/\/sii.pl\/blog\/?p=14195"},"modified":"2023-07-10T14:05:42","modified_gmt":"2023-07-10T12:05:42","slug":"swift-package-ci-with-github-actions-up-to-date-with-xcode-13-3","status":"publish","type":"post","link":"https:\/\/sii.pl\/blog\/en\/swift-package-ci-with-github-actions-up-to-date-with-xcode-13-3\/","title":{"rendered":"Swift Package CI with GitHub Actions. Up-to-date with Xcode 13.3!"},"content":{"rendered":"\n

This article is a continuation of the Quick and Simple Modularising Your Project with Swift Packages<\/a> tutorial where we created a local Swift Package and then moved it to the remote repository so we could reuse the module across multiple projects.<\/p>\n\n\n\n

This time, we will go through some additional setups, such as versioning the package, upgrading the package in your project, and creating simple CI with GitHub Actions. If you haven\u2019t read the previous article, I encourage you to do so to have the same starting point, however, that\u2019s not mandatory to complete the below steps.<\/p>\n\n\n\n

Versioning Swift Package<\/h2>\n\n\n\n

You are familiar with the Xcode App versioning system \u2013 you can change the version by opening your project settings in Xcode, selecting the app target, choosing the General tab, and changing the Version or\/and Build number, which appears in the repository as the change to MARKETING_VERSION<\/strong> and CURRENT_PROJECT_VERSION<\/strong> in .xcodeproj\/project\/pbxproj<\/strong> file.<\/p>\n\n\n\n

If you are using GitFlow, you are doing those steps and committing change during a new release which \u2013 upon finishing \u2013 is adding a new Git tag with the version number you specify.<\/p>\n\n\n\n

Here comes the beauty of the Swift Package. The versioning of your Package is much simpler as there is no file to edit the version. Your Package.swift<\/strong> configuration does not declare the Package version. All the magic happens with the Git tags! In fact, you don\u2019t even need to version your Swift Package, and you can use it by referring to the Git branch (which we did in the previous article), although, if you think of continuing developing your Package and keeping it public, it might be much more maintainable to start adding the version tags.<\/p>\n\n\n\n

Feel free to add the first version tag in your Package Git and call it 1.0.0. Don\u2019t forget to also change the Version Rules of your Package used in the project from Branch to Version.<\/p>\n\n\n\n

In Xcode, select your Project<\/strong> and under the Package Dependencies<\/strong> in the Packages<\/strong> section, double click your Package.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

The recommended rule is to use Version \u201cUp to Next Major\u201d.<\/p>\n\n\n\n

Press Done<\/strong> to finish.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n