swift-outdated for Mac

A swift subcommand for checking if your dependencies have an update available. This especially applies to updates outside of your version requirements.

Calling swift package update will only update to the latest available requirements inside your specified version requirements, which totally makes sense, but you might miss that there's a new major version available if you don't check the dependency's repository regularly.

This tool aims to help with that by allowing you to quickly check the remote git tags of your dependencies to see if something outside of your version requirements is available. It also aims to be smart regarding dependencies that are pinned to a branch or a specific revision, not checking transitive dependencies, following forks to their upstream, resolving package registry dependencies, checking for known security vulnerabilities, and supporting SwiftPM, Tuist and plain Xcode projects.

This project is very much inspired by cargo-outdated.

Installing

Homebrew

swift-outdated can be installed via Homebrew.

Mint

swift-outdated can also be installed via Mint.

Usage

Since swift-outdated installs with its name, it can be called just like a subcommand of Swift itself via swift outdated.

This lists all your outdated dependencies, the currently resolved version and the latest version available in their upstream repository.

Direct vs. transitive dependencies

By default swift-outdated only reports your project's direct dependencies, the ones you declared yourself, via swift package dump-package for SwiftPM and Tuist projects, and from the XCRemoteSwiftPackageReference entries in project.pbxproj for Xcode projects.

Pass -t / --include-transitive to report transitive dependencies as well. If the direct dependencies can't be determined (for example a project layout without a recognizable manifest), every package is reported.

Listing all dependencies

swift-outdated also allows listing all your dependencies alongside the ones that are not up to date.

Run the application using -u or --include-up-to-date command line switch and every dependency is listed in the same table. Up-to-date packages show a ✓ in the Latest column, and pins without any available information show a ?:

Following a fork's upstream

If a dependency is a fork of another project, the fork's own repository often carries no new tags, so it looks up to date even when the original (upstream) project has shipped newer releases. You can tell swift-outdated to measure outdatedness against the upstream instead, via a .swift-outdated.yml file in your project directory:

fork is matched against the URL in your Package.resolved (SSH/HTTPS and a .git suffix are treated the same); upstream is the repository whose tags then determine the latest version. The dependency is still listed under its own fork URL, only the version comparison, including the base/latest tags for branch and revision pins, uses the upstream.

Use --config / -c to point at a config file elsewhere.