Fix CI integration workflow for Bedrock without composer.lock#1656
Merged
Conversation
retlehs
force-pushed
the
fix/ci-composer-install
branch
4 times, most recently
from
cc510fd to
9ae648d
Compare
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
retlehs
force-pushed
the
fix/ci-composer-install
branch
from
9ae648d to
e99d2d0
Compare
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
1 participant
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
composer.lockfrom the repo (🔧 Remove lock file and relax dependency constraints bedrock#818)check-platform-reqstask fails without a vendor dir or lock filecomposer_platform_requirements_checkfor CI deploys since Bedrock no longer ships a lock file🤖 Generated with Claude Code