Output of `swift format --version` is confusing

[jkmathew]

I am using Xcode 16 which comes with a bundled swift format. When I run swift format --version, it prints main.
Does this mean the swift format bundled with Xcode will always be updated with the latest main branch? Or the bundled version is the latest from the main branch at the time of Xcode release is created?

I tried installing swift-format with homebrew and swift-format --version prints the version correctly.

[ahoppen]

Synced to Apple’s issue tracker as rdar://137309661

[allevato]

Unfortunately we've had to manually update the version number when cutting a release, and that can get overlooked easily. I know I've done it in the past.

IIRC, a recent change in SwiftPM has added a package API to query Git repository information and generate constants that we could reference from the --version handler instead. I would need to look further into it to see if that works as intended when a release is tagged and built.

cc @ahoppen who is in charge of releases.

[jkmathew]

I see there is already an automation implemented here
Tags containing proper versions like

swift-format/Sources/swift-format/PrintVersion.swift

Line 15 in 93ebb77

print("601.0.0-prerelease-2024-10-01")

I hope Xcode 16.1 release will have the proper version 🙂

[sdavids]

Still happens:

$ xcodebuild -version
Xcode 16.2
Build version 16C5032a
$ /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-format --version
main

[TTOzzi]

It doesn’t seem to be applied yet in Swift 6.1 (6.1.0.109.103) from Xcode 16.3 beta 2, but…

$ /Applications/Xcode-beta_16.3_2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift --version
swift-driver version: 1.120.5 Apple Swift version 6.1 (swiftlang-6.1.0.109.103 clang-1700.0.13.2)
Target: arm64-apple-macosx15.0

$ /Applications/Xcode-beta_16.3_2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-format --version
main

Since the automated version update script is running well on the latest pre-release of the release/6.1 branch, it will likely be resolved with the official release of Xcode 16.3(https://xcodereleases.com/) 🤔