Release name unnecessarily complicates scripts

[gonsolo]

Switching the release name from 601.0.0 to Swift 6.1.1 Release unnecessarily complicates things:
Arch Linux's "pkgctl version check" doesn't recognize the new release as it depends on the release starting with a number like 601 or simple prefixes like v601 that can be ignored.

I tried a few solutions (version-check.yaml, custom type, package-version.json, ...) and nothing works.
So please re-release with proper naming!

See for example:
https://github.com/RenderKit/embree/releases/tag/v4.4.0

[gonsolo]

Also the tar.gz is called swift-6.1.1-RELEASE.tar.gz not swift-format-RELEASE.tar.gz.

[gonsolo]

Also "swift-format -v" reports: "main"

[bnbarham]

The source tar is just the tag name. There's two types of releases here:

1. The semantic version for packages (synced with swift-syntax)
2. The toolchain tag when new toolchains are released (swift-<version>-RELEASE)

So in this case, a 6.1.1 was just released and thus a new tag and release added. But there's no real changes to swift-format, so there's no new 601.0.* tag. Having said that, for the tool (ie. not being used as a library) I would really expect the former (6.1.1) to be used rather than the latter (601.0.*) 🤔