chore: bump version to 1.3.0 by getappz · Pull Request #198 · getappz/agentflare

getappz · 2026-07-15T14:55:57Z

Summary

Bumps Cargo.toml version 1.2.0 -> 1.3.0 (minor: feat: commits since last release, no breaking changes) and regenerates Cargo.lock.
Updates the crate description to match the README/GitHub repo repositioning done in docs: README/STATUS refresh for coordination layer + prior pending commits #197.
release-plz's release-pr didn't auto-generate this: every workspace crate has publish = false and release-plz.toml has git_release_enable = false, so it has no crates.io/GitHub-release target and correctly produces no PR. Release publishing here is independent of release-plz -- it's driven by a v* tag push triggering release.yml's cross-compile pipeline.

Test plan

cargo check --workspace passes locally
CI status checks pass
After merge: push v1.3.0 tag to trigger release.yml

Summary by CodeRabbit

Chores
- Updated the package release version to 1.3.0.
- Refined the product description to highlight efficient AI coding agent execution and multi-agent coordination.

134 commits since v1.2.0 (2026-07-08), including multiple feat: commits (MCP tool consolidation, item FTS5 search, gateway/lean-ctx integration) and no breaking changes -- minor bump. Also updates the crate description to match the README/GitHub repo repositioning (optimization + coordination layer, not just cost optimization). release-plz's release-pr didn't generate this automatically: publish = false on every workspace crate plus git_release_enable = false in release-plz.toml means it has no crates.io or GitHub-release target to manage, so it correctly sees nothing to do. Actual release publishing here goes through release.yml on a v* tag push, independent of release-plz.

coderabbitai · 2026-07-15T14:56:18Z

📝 Walkthrough

Walkthrough

The agentflare crate version is bumped from 1.2.0 to 1.3.0, and its package description is updated in Cargo.toml.

Changes

Package metadata

Layer / File(s)	Summary
Update crate metadata `Cargo.toml`	The `agentflare` package version is set to `1.3.0`, and the description is changed to focus on running and coordinating AI coding agents.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

getappz/agentflare#159: Updates the same crate version in the root manifest.
getappz/agentflare#164: Modifies the same crate metadata fields.

Suggested reviewers: dependabot[bot], github-actions[bot]

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: a version bump to 1.3.0.
Description check	✅ Passed	It includes the required Summary and Test plan sections and is mostly complete, though the Notes for reviewers section is missing.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch worktree-release-1.3.0

_{Comment @coderabbitai help to get the list of available commands.}

coderabbitai

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@Cargo.toml`:
- Around line 7-10: Update the release workflow’s generation of
bucket/agentflare.json to source the package description from Cargo.toml instead
of hardcoding the previous text, ensuring the v1.3.0 Scoop manifest uses “Run AI
coding agents efficiently, and coordinate more than one of them.” Regenerate
bucket/agentflare.json so its description matches the new metadata.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 008e9122-ab41-4dac-9a43-4b320d39a5a1

📥 Commits

Reviewing files that changed from the base of the PR and between 1ad5b43 and 5a7d657.

⛔ Files ignored due to path filters (1)

Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

Cargo.toml

coderabbitai · 2026-07-15T14:58:54Z

+version = "1.3.0"
 edition = "2024"
 rust-version = "1.91"
-description = "Optimize AI CLI agents for cost and performance."
+description = "Run AI coding agents efficiently, and coordinate more than one of them."


🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Propagate the new description to release metadata.

.github/workflows/release.yml still hardcodes the previous description when generating bucket/agentflare.json, so the v1.3.0 Scoop manifest will publish stale metadata. Update the workflow to use this description as the single source of truth and regenerate bucket/agentflare.json as needed.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@Cargo.toml` around lines 7 - 10, Update the release workflow’s generation of bucket/agentflare.json to source the package description from Cargo.toml instead of hardcoding the previous text, ensuring the v1.3.0 Scoop manifest uses “Run AI coding agents efficiently, and coordinate more than one of them.” Regenerate bucket/agentflare.json so its description matches the new metadata.

…coding it CodeRabbit flagged this on #198: release.yml hardcoded the pre-rewrite description in both the Homebrew formula and Scoop manifest generation steps, so v1.3.0 would have shipped stale package-manager metadata even though Cargo.toml's description was just updated. Extract it at runtime instead so the two can't drift apart again. update-homebrew had no checkout step at all (it only clones the separate homebrew-agentflare repo) -- added one so Cargo.toml is actually available to read.

…carry item UUID (#595) Item #198 was auto-completed with zero implementation because find_duplicate_pr matched PR #636, whose footer said "for item #198" but whose content was a different item's work. The visible `for item #<N>` marker is only unique per project per workstation (each keeps its own item DB), so it can attribute one item's PR to another that shares the number. - pr_footer now appends a hidden `` tag; marks_this_item / find_by_item_marker reject a PR tagged for a different item. Untagged legacy PRs still fall back to the number. - handle_duplicate_pr: a merged match now skips dispatch and flags for human review like an open match, instead of mark_completed + cleanup_worktree + relabel_pr_completed on a text marker alone. - Regression tests for the incident shape (two items sharing #198) and the merged-duplicate-never-completes behavior. - Move worktree/mod.rs inline tests to mod_tests.rs (include!, as cli/work.rs does) so the file clears the 1500-line LOC gate. Agentflare-Agent: claude-code Agentflare-Branch: task/595-worktree-branch-identity-leaked-between Agentflare-Item: 595 Agentflare-Session: bc398774-1fe7-43e3-95ee-d2a16e38915c

…carry item UUID (#595) (#789) Item #198 was auto-completed with zero implementation because find_duplicate_pr matched PR #636, whose footer said "for item #198" but whose content was a different item's work. The visible `for item #<N>` marker is only unique per project per workstation (each keeps its own item DB), so it can attribute one item's PR to another that shares the number. - pr_footer now appends a hidden `` tag; marks_this_item / find_by_item_marker reject a PR tagged for a different item. Untagged legacy PRs still fall back to the number. - handle_duplicate_pr: a merged match now skips dispatch and flags for human review like an open match, instead of mark_completed + cleanup_worktree + relabel_pr_completed on a text marker alone. - Regression tests for the incident shape (two items sharing #198) and the merged-duplicate-never-completes behavior. - Move worktree/mod.rs inline tests to mod_tests.rs (include!, as cli/work.rs does) so the file clears the 1500-line LOC gate. Agentflare-Agent: claude-code Agentflare-Branch: task/595-worktree-branch-identity-leaked-between Agentflare-Item: 595 Agentflare-Session: bc398774-1fe7-43e3-95ee-d2a16e38915c

getappz enabled auto-merge July 15, 2026 14:56

coderabbitai Bot reviewed Jul 15, 2026

View reviewed changes

getappz merged commit 00a213b into master Jul 15, 2026
15 checks passed

getappz deleted the worktree-release-1.3.0 branch July 15, 2026 15:02

getappz mentioned this pull request Jul 15, 2026

ci(release): read description from Cargo.toml instead of hardcoding it #199

Merged

1 of 3 tasks

This was referenced Jul 15, 2026

chore(release): v1.3.1 #202

Merged

chore(release): agentflare v1.4.0 #225

Merged

coderabbitai Bot mentioned this pull request Jul 29, 2026

chore(release): agentflare v1.7.0 #371

Merged

getappz mentioned this pull request Aug 29, 2026

chore: Review sweep doesn't scale: serial per-item REST calls will exceed GitHub's rate limit at fleet scale #636

Merged

Navigation Menu

Repository navigation

chore: bump version to 1.3.0 - #198

chore: bump version to 1.3.0#198
getappz merged 1 commit into
masterfrom
worktree-release-1.3.0

getappz commented Jul 15, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

coderabbitai Bot commented Jul 15, 2026 •

edited

Loading

Walkthrough

Changes

Uh oh!

coderabbitai Bot left a comment

Uh oh!

coderabbitai Bot Jul 15, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

getappz commented Jul 15, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Test plan

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented Jul 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot Jul 15, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

getappz commented Jul 15, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Jul 15, 2026 •

edited

Loading