Post-1.1.0, feat commits no longer drive minor bumps on every release:
versioning switches to always-bump-patch, so the next release is 1.1.1
regardless of commit types. Minor/major releases become deliberate
decisions via a Release-As footer (same mechanism used to cut 1.0.0).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The v1.0.0 release build failed at cargo update --workspace: release-please
bumps the workspace package version via extra-files, but llmfit-tui pins
llmfit-core with an explicit version requirement that stayed at ^0.9.0.
Bump it and register the pin in release-please extra-files so future
releases keep it in sync.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The rust release type expects explicit version fields in each subcrate
Cargo.toml, but this workspace uses version.workspace = true. Switch to
simple type with an extra-files entry to bump the workspace version in
the root Cargo.toml.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Replaces manual tag-and-push workflow with release-please, which
auto-creates release PRs with version bumps and changelogs on merge
to main. Existing release.yml build pipeline is unchanged — it still
triggers on v* tags created by release-please.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
