chore: bump version to 0.1.22

[ilya-bogin-keenable]

Bumps the version to 0.1.22 to release the X-Keenable-Title fix (#45).

The CLI now sends the header the backend requires on token-less (public) endpoints, so the unauthenticated free-tier flow works again. Until this ships in a release, users on 0.1.21 still hit 400 Missing app identifier, and the nightly e2e (which installs the released binary) stays red.

Merging this, then tagging v0.1.22, triggers release.yml (cargo-dist) to build and publish the binaries.

🤖 Generated with Claude Code

[qodo-code-review]

PR Summary by Qodo

Bump crate version to 0.1.22 for release
⚙️ Configuration changes 🕐 Less than 5 minutes

Description

• Bump keenable-cli package version from 0.1.21 to 0.1.22.
• Prepares a tagged v0.1.22 release to ship the X-Keenable-Title fix.

High-Level Assessment

The following are alternative approaches to this PR:

1. Automate versioning via release tooling

• ➕ Reduces manual version-bump PRs and potential mistakes
• ➕ Can enforce consistent tagging/changelog generation
• ➖ Upfront setup cost and workflow changes
• ➖ May not fit the current cargo-dist/release.yml process without adjustments

2. Use `cargo set-version` in a standardized release script

• ➕ Keeps manual control while standardizing the process
• ➕ Minimizes human error (updates other manifests if added later)
• ➖ Still requires a dedicated bump commit/PR
• ➖ Adds a tooling dependency/step for maintainers

Recommendation: Current approach is appropriate for an immediate patch release: a direct Cargo.toml version bump is low risk and aligns with tagging-based release triggers. Consider automating version bumps later if releases become frequent or multi-file versioning emerges.

Files changed (1) +1 / -1

Other (1) +1 / -1

Cargo.tomlBump crate version to 0.1.22 +1/-1

Bump crate version to 0.1.22

• Updates the package version from 0.1.21 to 0.1.22 to prepare the next release build and publish step.

Cargo.toml

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review