Skip to content

fix(deps): update dependency js-yaml to v5 - autoclosed #63

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

Closed
renovate wants to merge 1 commit into from
Closed

fix(deps): update dependency js-yaml to v5 - autoclosed #63

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
20 changes: 15 additions & 5 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@
"@types/jsonwebtoken": "^9.0.10",
"dotenv": "^17.0.0",
"express": "^5.0.0",
"js-yaml": "^4.1.1",
"js-yaml": "^5.0.0",

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 22, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Preserve YAML merge handling for model allowlists

When litellm_config.yaml uses YAML merge keys to share model definitions (for example entries whose model_name or litellm_params come from <<: *defaults), js-yaml v5 no longer applies those merges under the default load() schema. In this app that makes getAllowedModels() miss the inherited models and can return an empty list, after which isModelAllowed() treats every requested model as allowed, so a config that was restrictive under v4 silently becomes fail-open; add the v5 merge tag/schema when loading this config or otherwise preserve the previous allowlist semantics.

Useful? React with 👍 / 👎.

"jsonwebtoken": "^9.0.2",
"zod": "^4.0.0"
},
Expand Down
Loading