chore(main): release arize-phoenix 5.0.0 #4707
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
5.0.0 (2024-09-26)
Phoenix 5.0 ships with authentication. Once enabled, Phoenix's UI and APIs (REST, GraphQL, and gRPC) are accessible only to users who present valid access and refresh tokens issued at sign in (session-based authentication) or API keys created within the app (key-based authentication).
Phoenix 5.0 also introduces basic RBAC (role-based access control). With RBAC you get admins (who can create, edit, and delete users) and members (who can edit only their own profile).
Phoenix 5.0 adds API keys so that you can securely ingest and query for data.
Phoenix 5.0 also adds OAuth2 (Google, AWS Cognito, Auth0) support as well as SMTP for password resets.
⚠ BREAKING CHANGES
Features
/exports
when auth is enabled (#4589) (b7af851)Secure
attribute on cookies (#4520) (655a459)Bug Fixes
exp
fromjwt
(#4729) (0e6e1e8)Documentation
This PR was generated with Release Please. See documentation.