arize-phoenix: v21.0.0
Arize Phoenix v21.0.0 enables authentication by default, adds DECISION and AGENT annotation kinds, fetches model cost manifests at runtime, and introduces a system state table alongside critical database and auth fixes.
原始内容为英文；当前页面提供中文导航与来源说明，具体事实请以原文为准。
为什么值得关注
Arize Phoenix release v21.0.0 represents a major version update with significant architectural, authentication, and database modifications. Key features include: - Authentication enabled by default even without explicitly configuring PHOENIX SECRET . - New annotation kinds: DECISION and AGENT . - Addition of a system state table. - Dynamic runtime fetching of the model cost manifest. - Robust cost-tracking improvements including $0 token price preservation, soft deletion of retired built-in models linked to SpanCost , and fallback price requirements for ManifestModel . - Database changes requiring user IDs on API keys and password reset tokens, foreign key ON DELETE rule alignment for ORM operations, and running SQLite migrations through sqlean . - Authentication hardening around OAuth2 sessions, state bindings, and atomic replacement of password reset tokens.
可执行摘要
Arize Phoenix v21.0.0 introduces breaking and major configuration changes: authentication is enabled by default without requiring PHOENIX SECRET, and annotations now support DECISION and AGENT kinds. Cost tracking fetches manifests at runtime with enhanced handling of zero token pricing, fallback models, and deduplication. Extensive database schema updates enforce user IDs on API keys and password reset tokens,…
- Agent 实用度
- 96/100
- 可信度
- 96%
- 机器格式
- JSON + Markdown
开发者应核对什么
- Review MIGRATION.md before upgrading, as authentication is now enabled by default without requiring PHOENIX SECRET.
- Verify that custom API keys and password reset tokens in database scripts satisfy the new non-null user ID requirement.
- Ensure environment configurations align with default admin upgrade credentials (PHOENIX DEFAULT ADMIN INITIAL PASSWORD) and OAuth2 cookie changes.
- Validate that SQLite environments are compatible with sqlean for running Alembic migrations.