Skip to content

fix: php sdk publishing workflow#726

Merged
maxprilutskiy merged 1 commit intomainfrom
devin/1746225598-fix-php-sdk-publishing
May 3, 2025
Merged

fix: php sdk publishing workflow#726
maxprilutskiy merged 1 commit intomainfrom
devin/1746225598-fix-php-sdk-publishing

Conversation

@devin-ai-integration
Copy link
Copy Markdown
Contributor

PHP SDK Publishing Workflow Fix

Problem

The current PHP SDK publishing workflow was failing at the "Install dependencies for SDK" step because the version field validation was happening before the workflow had a chance to set a valid version.

Solution

  1. Moved the version check and setting logic to occur before the composer install step
  2. Set a default version in the PHP SDK's composer.json
  3. Added better error handling for version bumping
  4. Added debug logging for Packagist publishing

This fix ensures that on every push to main affecting the PHP SDK, a new version will be automatically published to Packagist with an incremented patch version.

Link to Devin run: https://app.devin.ai/sessions/6407d462e80c47b4b98a7af1e3565247
User: Max Prilutskiy (max@lingo.dev)

Co-Authored-By: Max Prilutskiy <maks.prilutskiy@gmail.com>
@devin-ai-integration
Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@devin-ai-integration devin-ai-integration bot changed the title Fix PHP SDK publishing workflow fix: php sdk publishing workflow May 2, 2025
@maxprilutskiy maxprilutskiy merged commit 690a38a into main May 3, 2025
3 of 4 checks passed
@maxprilutskiy maxprilutskiy deleted the devin/1746225598-fix-php-sdk-publishing branch May 3, 2025 01:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant