Skip to content

chore: bump version to 0.2.0 - #64

Merged
ilya-bogin-keenable merged 1 commit into
mainfrom
bump-0.2.0
Aug 13, 2026
Merged

chore: bump version to 0.2.0#64
ilya-bogin-keenable merged 1 commit into
mainfrom
bump-0.2.0

Conversation

@ilya-bogin-keenable

Copy link
Copy Markdown
Contributor

Version bump for the release that ships #63 (removal of the feedback subcommand).

Minor rather than the usual patch bump: keenable feedback is gone, which breaks anyone scripting it — worth signalling in the version even on 0.x. (The command already fails against the live API: /v1/feedback returns 404 on both api.keenable.ai and api-test.keenable.ai.)

Tag v0.2.0 follows once this lands, which triggers the dist release workflow.

🤖 Generated with Claude Code

Minor bump rather than the usual patch: removing the `feedback` subcommand
(#63) breaks anyone scripting it, so signal that in the version.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@ilya-bogin-keenable
ilya-bogin-keenable merged commit 1bb12d4 into main Aug 13, 2026
12 checks passed
@ilya-bogin-keenable
ilya-bogin-keenable deleted the bump-0.2.0 branch August 13, 2026 15:56
@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Bump keenable-cli version to 0.2.0

⚙️ Configuration changes 🕐 Less than 5 minutes

Grey Divider

AI Description

• Bump crate version from 0.1.26 to 0.2.0 in Cargo manifest and lockfile
• Prepare the v0.2.0 tag/release to signal a breaking CLI surface change
High-Level Assessment

The following are alternative approaches to this PR:

1. Automate versioning via cargo-release (or similar)
  • ➕ Reduces manual edits and risk of forgetting Cargo.lock updates
  • ➕ Standardizes tagging/changelog/version bump workflow
  • ➖ Adds tooling/CI assumptions and developer setup
  • ➖ May be overkill for a small project
2. Derive version from git tag in release pipeline (no in-repo bump)
  • ➕ Single source of truth is the release tag
  • ➕ Avoids version-only PRs
  • ➖ Crate publishing typically expects Cargo.toml version to match the published artifact
  • ➖ Can complicate local builds and dependency resolution

Recommendation: Current approach is fine for a simple release prep PR. If version bumps become frequent or error-prone, adopt cargo-release (or an equivalent scripted workflow) to ensure consistent version/tag updates and reduce manual bookkeeping.

Files changed (2) +2 / -2

Other (2) +2 / -2
Cargo.lockUpdate lockfile package version to 0.2.0 +1/-1

Update lockfile package version to 0.2.0

• Bumps the recorded version for the keenable-cli package from 0.1.26 to 0.2.0 in the generated lockfile to stay consistent with the manifest.

Cargo.lock

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

Bump crate version to 0.2.0

• Updates the keenable-cli package version from 0.1.26 to 0.2.0 to prepare the next release.

Cargo.toml

@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

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

Grey Divider

Great, no issues found!

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

Grey Divider

Tip of the day
💡 Did you know, you can type 'qodo, fix this' on a finding and the fix lands right on your PR

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant