chore: bump version 1.5.0 -> 1.6.0 (Gemini 2.5 Flash release)#24
Conversation
PR #23 added the real Gemini 2.5 Flash adapter (replacing the placeholder); 1.5.0 ships as placeholder, so the Gemini-enabled release goes out as 1.6.0. Live verification: anthropic ✅, gemini ✅. OpenAI not verified due to user-side key issue (provider code unchanged). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ae23e2e2ac
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| [project] | ||
| name = "omegaprompt" | ||
| version = "1.5.0" | ||
| version = "1.6.0" |
There was a problem hiding this comment.
Keep the uv lockfile version in sync
Bumping the project metadata here without regenerating uv.lock leaves the editable omegaprompt package locked at version = "1.5.0" in uv.lock (checked around uv.lock:791-794). uv lock --help describes the lockfile as the project's lockfile and provides --check to verify it is up to date, so any release or developer workflow that uses locked uv state can either fail the freshness check or continue reporting/installing the local project as 1.5.0 instead of this 1.6.0 release.
Useful? React with 👍 / 👎.
Release of the real Gemini 2.5 Flash adapter (PR #23). 1.5.0 shipped as placeholder; 1.6.0 is the first release with the live adapter.
Live smoke verified: anthropic ✅, gemini ✅. OpenAI not verified (user-side key issue, no provider code change).
🤖 Generated with Claude Code