fix(ci): include litellm-config.yaml in RC docker-compose bundle#4652
Merged
Conversation
The single-node docker-compose.yml bind-mounts ./litellm-config.yaml into the litellm container, but the RC bundling step never copies it. When the file is absent on the host, Docker creates an empty directory at the mount target, causing litellm to fail with IsADirectoryError on /app/config.yaml. Closes apache#4651 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4652 +/- ##
============================================
- Coverage 52.46% 46.76% -5.71%
- Complexity 0 2069 +2069
============================================
Files 353 1013 +660
Lines 21338 39571 +18233
Branches 1791 3852 +2061
============================================
+ Hits 11195 18504 +7309
- Misses 10026 20281 +10255
- Partials 117 786 +669
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
bobbai00
added
the
release/v1.1.0-incubating
Yicong-Huang
approved these changes
May 2, 2026
Yicong-Huang
added a commit
that referenced
this pull request
May 2, 2026
…4678) ## What changes were proposed in this PR? In \`.github/workflows/auto-queue.yml\`, replace the \`mergeStateStatus === 'BEHIND'\` filter with an iteration over eligible auto-merge PRs (non-draft, non-conflicting). For each candidate, call \`updateBranch\`; on failure (already up-to-date / merge conflict / etc.), warn and try the next. Stop at the first PR that actually got updated. ## Any related issues, documentation, discussions? Follow-up to #4672. Observed in [run 25248773692](https://github.com/apache/texera/actions/runs/25248773692/job/74037400879): the workflow fired ~3s after a push to main, when GitHub had not yet recomputed \`mergeStateStatus\` for open PRs. PR #4652 (\`mergeable=MERGEABLE\`, \`autoMergeRequest != null\`) was a real candidate but its \`mergeStateStatus\` was \`UNKNOWN\` at query time, so the strict \`=== 'BEHIND'\` filter dropped it and the run logged "No auto-merge PRs need updating". \`mergeStateStatus\` is documented as computed asynchronously, and there's no reliable bound on how long it stays \`UNKNOWN\` after a base-branch push. Letting \`updateBranch\` decide whether there's actual work to do is more robust than depending on a flaky pre-flight signal. ## How was this PR tested? Not yet — workflow runs only on push-to-main. Will observe behavior on the next merge. ## Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Opus 4.7 (Claude Code)
github-actions Bot
pushed a commit
that referenced
this pull request
May 2, 2026
### What changes were proposed in this PR? Adds the missing `cp` of `bin/single-node/litellm-config.yaml` into the bundle directory in the `Create Docker Compose deployment bundle` step of `.github/workflows/create-release-candidate.yml`. `bin/single-node/docker-compose.yml` bind-mounts the file: ```yaml volumes: - ./litellm-config.yaml:/app/config.yaml:ro ``` Without this copy, the RC tarball ships without `litellm-config.yaml`. When users extract it and run `docker compose up`, Docker creates an empty directory at the bind source, and litellm crashes with `IsADirectoryError: '/app/config.yaml'`. ### Any related issues, documentation, discussions? Closes #4651 ### How was this PR tested? To be verified by re-running the `Create and upload release candidate artifacts` workflow against the next RC tag and confirming `litellm-config.yaml` is present in the docker-compose tarball and that `docker compose up` starts the litellm container cleanly. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Opus 4.7) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> (backported from commit de64d70)
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
3 participants
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.
What changes were proposed in this PR?
Adds the missing
cpofbin/single-node/litellm-config.yamlinto the bundle directory in theCreate Docker Compose deployment bundlestep of.github/workflows/create-release-candidate.yml.bin/single-node/docker-compose.ymlbind-mounts the file:Without this copy, the RC tarball ships without
litellm-config.yaml. When users extract it and rundocker compose up, Docker creates an empty directory at the bind source, and litellm crashes withIsADirectoryError: '/app/config.yaml'.Any related issues, documentation, discussions?
Closes #4651
How was this PR tested?
To be verified by re-running the
Create and upload release candidate artifactsworkflow against the next RC tag and confirminglitellm-config.yamlis present in the docker-compose tarball and thatdocker compose upstarts the litellm container cleanly.Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Opus 4.7)