Skip to content

chore: bump version 1.5.0 -> 1.6.0 (Gemini 2.5 Flash release) #24

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
hibou04-ops merged 1 commit into from
May 6, 2026
Merged

chore: bump version 1.5.0 -> 1.6.0 (Gemini 2.5 Flash release) #24

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
25 changes: 25 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,31 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),

## [Unreleased]

## [1.6.0] - 2026-05-06

### Added

- **Real Gemini 2.5 Flash provider** (replaces the prior placeholder). Uses the official Google GenAI SDK (`google-genai`) with freeform / JSON-object / strict-schema (`response_schema`) request paths plus local Pydantic validation. Default model: `gemini-2.5-flash`. Live single-call smoke test verified against `gemini-2.5-flash` (input_tokens=21, output_tokens=2 normalized correctly).
- **Capability declaration**: `tier=cloud`, `supports_strict_schema=True`, `supports_json_object=True`, `supports_llm_judge=True`, `ship_grade_judge=False` — guarded judge use requires separate validation; expedition profile may fall back to JSON-object output + local validation with a `CapabilityEvent`.
- **Env key resolution**: `_ENV_KEYS_FOR_PROVIDER` accepts `GEMINI_API_KEY` or `GOOGLE_API_KEY` (tuple form, per-provider).
- **`google-genai>=1.0.0` dependency** added to base `dependencies`; new `gemini` extra for slim installs.

### Changed

- `normalize_usage` handles Gemini's `prompt_token_count` / `candidates_token_count` / `total_token_count` fields in addition to OpenAI/Anthropic field names.
- README provider matrix, capability table, and sample commands updated to describe the real adapter.
- `LLMProvider` Protocol unchanged — Anthropic/OpenAI/local adapters are not modified in this release.

### Test

- 41 provider tests pass (mock-based for all three vendors).
- Live verification: Anthropic ✅ (claude-opus-4-7), Gemini ✅ (gemini-2.5-flash). OpenAI not verified due to user-side API key issue (provider code unchanged from 1.5.0).

### Notes

- Reasoning profiles (`LIGHT`/`DEEP`) emit a `CapabilityEvent` for Gemini because this adapter does not map them to a native Gemini control. `OFF` / `STANDARD` work without events.
- Gemini judge is not marked `ship_grade_judge=True`. Validate independently before treating Gemini-judged artifacts as ship-ready under guarded mode.

## [1.4.0] - 2026-04-29

IP defense package + cross-toolkit AGENT_TRIGGERS guide. Same eight runtime entrypoints + MCP server as 1.3.0; this release ships the previously-out-of-tree authorship and trigger artefacts inside the PyPI sdist for parity with the rest of the toolkit and adds the canonical agent-trigger cookbook.
Expand Down
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ build-backend = "hatchling.build"

[project]
name = "omegaprompt"
version = "1.5.0"
version = "1.6.0"
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot May 6, 2026

Choose a reason for hiding this comment

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

P2 Badge 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 👍 / 👎.

description = "Provider-neutral prompt calibration engine with sensitivity-ranked meta-axes, hard-gate x soft-score fitness, walk-forward ship gates, guarded/expedition profiles, and explicit capability/risk reporting across Anthropic, OpenAI, Gemini, and local OpenAI-compatible backends. Optional sub-tools (mini-omega-lock, mini-antemortem-cli) distribute separately and plug in via the omegaprompt.preflight interface."
readme = "README.md"
requires-python = ">=3.11"
Expand Down
2 changes: 1 addition & 1 deletion src/omegaprompt/__init__.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@
report,
)

__version__ = "1.5.0"
__version__ = "1.6.0"

__all__ = [
# domain
Expand Down
Loading