Skip to content

chore: bump version to 0.2.1 #66

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
IlyaGusev merged 1 commit into from
Aug 16, 2026
Merged

chore: bump version to 0.2.1 #66

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "keenable-cli"
version = "0.2.0"
version = "0.2.1"

@qodo-code-review qodo-code-review Bot Aug 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remediation recommended

1. Release docs version mismatch 🐞 Bug ⚙ Maintainability

After bumping the crate to 0.2.1, RELEASE.md still instructs running cargo set-version 0.2.0 and
tagging v0.2.0, which can lead to cutting/pushing the wrong tag and producing a release that
doesn’t match the code’s declared version.
Agent Prompt 
## Issue description
The crate version is now 0.2.1, but `RELEASE.md` still hardcodes `0.2.0` in the example commands. This can lead maintainers to accidentally set/tag the wrong version during the release process.

## Issue Context
The release workflow is tag-driven, so the tag you create/push matters.

## Fix Focus Areas
- RELEASE.md[5-19]
- Cargo.toml[1-6]
- .github/workflows/release.yml[20-46]

## Suggested fix
Update the hardcoded `0.2.0` examples in `RELEASE.md` to `0.2.1`, or (preferably) replace hardcoded versions with a placeholder (e.g. `<version>`) to avoid future staleness.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

edition = "2024"
description = "Keenable CLI — authenticate, manage API keys, configure MCP, and search the web"
authors = ["grigorevp <grigoryev.pete@gmail.com>"]
Expand Down
Loading