chore: release v0.5.0 - #43
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
@codex review |
|
To use Codex here, create a Codex account and connect to github. |
Summary of ChangesHello @diegosouzapw, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request marks the release of version 0.5.0, bringing a substantial upgrade to the application. It focuses on expanding core functionalities such as LLM evaluation and routing strategies, significantly improving the user interface and experience, and bolstering the underlying architecture for better stability and maintainability. The update also includes a range of bug fixes and an increase in test coverage, ensuring a more robust and feature-rich platform. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request prepares for the v0.5.0 release by updating the version number in various files and adding a new changelog entry. While the version bumps are correct, I've identified a couple of inconsistencies in the changelog that should be addressed before merging. Specifically, the release date is set in the future, and a new feature mentioned in the release notes appears to be missing from the codebase.
|
|
||
| - **Random Strategy** — Random model selection for even distribution | ||
| - **Least-Used Strategy** — Routes to the least recently used model using combo metrics | ||
| - **Cost-Optimized Strategy** — Leverages pricing infrastructure to route to cheapest available model |
There was a problem hiding this comment.
The changelog states that a Cost-Optimized Strategy has been added for combo routing. However, this strategy is not implemented in src/domain/comboResolver.js. While docs/openapi.yaml includes cost-optimized as a valid enum value, the corresponding implementation seems to be missing from the codebase. Please either include the code for this feature or remove it from the release notes to avoid confusion.
|
|
||
| --- | ||
|
|
||
| ## [0.5.0] — 2026-02-15 |
There was a problem hiding this comment.
The release date is set to 2026-02-15, which is in the future. This is likely a placeholder or a typo and should be updated to the actual release date.
There was a problem hiding this comment.
Pull request overview
Release housekeeping for v0.5.0, aligning published metadata (npm + OpenAPI) and user-facing release docs (README + changelog) with the new version.
Changes:
- Bump version references from
0.4.0→0.5.0(npm metadata + OpenAPI spec). - Update release instructions in README for the new tag.
- Add a new
0.5.0section toCHANGELOG.mddescribing new features/fixes.
Reviewed changes
Copilot reviewed 4 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
package.json |
Updates npm package version to 0.5.0. |
package-lock.json |
Updates lockfile package version to 0.5.0 and reflects current bin mappings. |
docs/openapi.yaml |
Updates OpenAPI info.version to 0.5.0. |
README.md |
Updates the example GitHub release command to v0.5.0. |
CHANGELOG.md |
Adds the 0.5.0 release notes section. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ## [0.5.0] — 2026-02-15 | ||
|
|
||
| Dashboard refinements, LLM evaluation framework, combo strategies expansion, and UI/UX polish. | ||
|
|
There was a problem hiding this comment.
The changelog now jumps from v0.5.0 directly to v0.3.0 and there is no v0.4.0 section in this file. Since the project version is being bumped from 0.4.0 → 0.5.0, please add a v0.4.0 entry (or adjust the existing sections) so the release history is consistent.
| - **Race Condition Fix** — `route.js` `ensureInitialized()` replaced boolean flag with Promise-based singleton to prevent parallel initialization | ||
| - **Domain State Persistence** — SQLite-backed persistence for 4 domain modules via `domainState.js` | ||
| - **Write-Through Cache** — In-memory Map + SQLite write-through for state survival across restarts | ||
| - **Race Condition Fix** — `route.js` `ensureInitialized()` with Promise-based singleton |
There was a problem hiding this comment.
This entry claims a race condition fix via a Promise-based singleton in route.js ensureInitialized(), but several API routes still use a boolean initialized flag (e.g., src/app/api/v1/api/chat/route.js, src/app/api/v1/messages/route.js, src/app/api/v1/responses/route.js). Please either update the changelog wording to reference only the specific route(s) that use the Promise-based approach, or align the remaining routes so the claim is accurate.
| - **Race Condition Fix** — `route.js` `ensureInitialized()` with Promise-based singleton | |
| - **Init Race Mitigation (Partial)** — Introduced Promise-based `ensureInitialized()` helper in `route.js` for affected routes |
Records both rounds of the independent audit in FINAL_THREE_AGENT_REVIEW, and restructures the file by release line so the v3.8.51 record stays intact underneath its own heading instead of being overwritten. Round 1, on 20d5b2c: three auditors in parallel, no access to each other's conclusions. Two HIGH (the decision store bounded only by count, and the webhook wizard leaving an enabled all-events webhook behind on cancel), plus the medium, low and improvement findings, each with where it was fixed. Round 2, the verification round on the final tree 68a00d0: the same three auditors re-checking their own fixes. None was found missing, partial or wrong. All three returned PASS with CRITICAL 0 and HIGH 0. The behaviour evidence that mattered most for this release is recorded: provider selection identical to v3.8.53 over 700 of 700 seeded cases, and previewRoutingDecision calling Math.random zero times over 200 previews with the rotator provably untouched. The findings round 2 raised were fixed, not deferred (#41, #42, #43). The only item accepted without a fix is B-03 / R-10, js-yaml 4.3.1 in the Electron update-check chain — not in the container image, the npm package or the server runtime. AUTONOMOUS_MISSION_STATE moves to CANDIDATE_COMPLETED -> RELEASING, with the phase table, the verification round, the Windows-only gate failures, and a note that the publication evidence has to live in the Release notes because publishing the Release locks this branch. Verification (isolated env): check-doc-links exit 0 172 docs, 1043 internal links check-fabricated-docs exit 0 check-docs-frontmatter exit 0 check-changelog-integrity exit 0 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Version bump to 0.5.0 with updated changelog, package.json, README, and OpenAPI spec.