chore(release): agentflare v1.4.0 - #225
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe package version changes from 1.3.1 to 1.4.0, the changelog gains a dated 1.4.0 release entry, and the site footer badge is updated to display v1.4.0. ChangesRelease metadata
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
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 `@CHANGELOG.md`:
- Line 10: Update the release references in site/public/index.html and
site/src/worker.ts from v1.3.1 to v1.4.0 so the website and installer
consistently serve the newly published release. Keep the existing reference
format and surrounding release logic unchanged.
🪄 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: 69cb7295-f055-455e-b931-7e59d8cba961
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (2)
CHANGELOG.mdCargo.toml
|
|
||
| ## [Unreleased] | ||
|
|
||
| ## [1.4.0](https://github.com/getappz/agentflare/compare/v1.3.1...v1.4.0) - 2026-07-17 |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Propagate the 1.4.0 version to site release references.
The release entry is being published as 1.4.0, but site/public/index.html:529 and site/src/worker.ts:19 still reference v1.3.1. Update those references, or make the release workflow generate them, so the website and installer do not continue serving the previous release.
🤖 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 `@CHANGELOG.md` at line 10, Update the release references in
site/public/index.html and site/src/worker.ts from v1.3.1 to v1.4.0 so the
website and installer consistently serve the newly published release. Keep the
existing reference format and surrounding release logic unchanged.
|
Addressed: bumped the site badge (index.html) to v1.4.0. Left |
… bloat (#277) * feat(npm): switch from preinstall-download to optionalDependencies + runtime shim Drops the preinstall script (installArchSpecificPackage.js) that manually shelled out to npm install for the detected platform package. Replaces it with: - main package declares all 5 platform packages as optionalDependencies (npm/yarn/pnpm resolve+fetch+verify only the one matching this machine's os/cpu natively -- the same mechanism already used for every other dependency, no reimplementation needed) - bin/agentflare.js is a small shim that at *invocation* time (not install time) resolves whichever platform package actually got installed and execs it, forwarding argv/stdio/exit code No script runs at npm install time anymore. Validated end-to-end with real npm-packed tarballs (not just file: links, which have unrelated relative-path quirks): install produces no lifecycle-script output, the shim resolves and execs the platform binary, forwards arguments, and propagates the exit code correctly. Also caught and fixed a real trailing-comma bug in the optionalDependencies JSON-generation while validating (bash %-pattern stripping needs the backslash unescaped inside a single-quoted pattern, confirmed by direct testing). Item #225. Holding this on its branch, uncommitted to master, until there's a batch of other changes ready to release together. * fix(hook): sync session hooks with actual feature state, cut per-turn bloat session_start's closing status line and prompt_submit's per-turn identity bits claimed lean-ctx/Exa/MCP tooling was active unconditionally, even when the matching component wasn't installed or registered. Gate both on each component's own check() instead. prompt_submit also repeated four full sentences into every turn's context forever; now sent once per session (first turn only) in the terse @tag: syntax already used by the rule files, instead of every turn. session_start's section headings get brand-matching color (same codes as banner::colorize), gated on NO_COLOR. * refactor(hook): compute components once per prompt_submit turn CodeRabbit nitpick: identity_bits() and the pending-consent check each called get_components(), which does file/JSON I/O per component, on every first-turn prompt. Pass the already-computed list into identity_bits instead of recomputing it.
Version bump + changelog for v1.4.0 (59 commits since v1.3.1: GitHub module, cliclack UI, optimize/CCR retrieve, PM skill pack, LOC gate, gateway idempotency fix, and more — see CHANGELOG.md).
release-plz's automated release-pr found nothing to do (workspace
publish = false), so this bump is hand-authored from the conventional-commit log.After merge: push tag
v1.4.0to triggerrelease.yml(binary builds + GitHub Release + Homebrew/Scoop/npm/PPA/Docker fan-out).Summary by CodeRabbit
Documentation
Chores