Bump llm to 0.4.3#515
Merged
Merged
Conversation
1b4b800 to
d4aa288
Compare
d4aa288 to
49ea012
Compare
vitramir
approved these changes
May 20, 2026
This was referenced May 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
llm_chart_versionfrom0.4.2to0.4.30.4.3includes the LLM service authz tuple write onCreateModel, which is required for llm-proxycan_usechecks against models created during E2EWhy
Chat-app E2E logs show llm-proxy 403s for API-token-authenticated agent processes:
Those models resolve successfully in the LLM service, but OpenFGA has no
organization:<org_id>, org, model:<model_id>tuple, socan_use: member from orgcannot resolve. Bootstrap was still deployingllmchart0.4.2; the tuple-write fix is inllm0.4.3.Tests
terraform fmt -check -recursive