[WIP] Fix the failing GitHub Actions workflow for Test Examples#800
Merged
lpcox merged 2 commits intoclaude/enable-api-proxy-by-defaultfrom Feb 13, 2026
Merged
Conversation
Co-authored-by: lpcox <15877973+lpcox@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
Files not reviewed (1)
- containers/api-proxy/package-lock.json: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
3 tasks
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
2 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.
Summary
Fixed the failing "Test Examples" workflow by adding the missing
package-lock.jsonfile to thecontainers/api-proxy/directory.Root Cause: The api-proxy Dockerfile uses
npm ci --only=productionwhich requires a package-lock.json file. The file was missing from the repository, causing the Docker build to fail.Solution: Generated package-lock.json (lockfileVersion 3) with all dependencies for express and http-proxy-middleware properly locked.