0.5.0
Pre-release
0.5.0 (272)
⚠️ Breaking changes
Two, both of which need a decision before upgrading.
Commit messages are read as Conventional Commits
Finch now expects type(scope): description rather than its own [tag] description convention. The type and every scope become tags, so feat(app-store): … carries both feat and app-store, and --required-tags app-store goes on matching. A ! before the colon, or a line opening BREAKING CHANGE:, adds a breaking tag.
If your history uses [tag] subjects, changelogs will come out empty or unsectioned until you opt back in. One line, and nothing else about your configuration changes:
format:
commit_style: delimited--commit-style conventional|delimited overrides it for a single run, which is what you want when comparing versions either side of a migration.
The default sections gained a Breaking Changes heading, and fix joined Bug Fixes so the defaults suit either convention.
Building from source requires a Swift 6.0 toolchain
Finch builds in the Swift 6 language mode. That applies to Homebrew, Mint and make install; the Finch.pkg attached below is a prebuilt binary and needs nothing beyond macOS. The Homebrew formula declares Xcode 16 as a build dependency, so a stale toolchain now fails with a sentence rather than an error from inside SwiftPM.
Also worth knowing
- Tags are parsed from the commit message rather than the whole log line, so an author address such as
dependabot[bot]@…no longer contributes a phantombottag. - A
[tag]: descriptionsubject no longer keeps its colon once the tag is removed.
Features
- Read Conventional Commits by default - PR #153