Skip to content

Conversation

@kojiromike
Copy link
Contributor

@kojiromike kojiromike commented Jan 17, 2026

Summary

  • Chains build-phar workflow from release-please using workflow_call (fixes GITHUB_TOKEN not triggering other workflows)
  • Adds build-phar-on-release.yml wrapper for manual release: created events
  • Adds optional tag_name input to workflow_dispatch for attaching PHAR to existing releases
  • Fixes checkout to use the tag ref when tag_name is provided
  • Updates build.php to determine version from BUILD_VERSION env var or git describe --tags

Fixes #20

🤖 Generated with Claude Code

GitHub Actions events triggered by GITHUB_TOKEN don't trigger other
workflows (security feature to prevent loops). This meant the build-phar
workflow never ran when release-please created releases.

Changes:
- Convert build-phar to reusable workflow (workflow_call) and call it
  directly from release-please after release creation
- Add build-phar-on-release.yml wrapper for manual release events
- Add optional tag_name input to workflow_dispatch for attaching PHAR
  to existing releases
- Fix checkout to use tag ref when tag_name is provided
- Update build.php to get version from BUILD_VERSION env var or git
  describe instead of hardcoded value

Fixes #20

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@kojiromike kojiromike force-pushed the release-please-chain branch from 2d35b45 to 533effc Compare January 17, 2026 03:55
@kojiromike kojiromike merged commit 69b514f into main Jan 17, 2026
7 checks passed
@kojiromike kojiromike deleted the release-please-chain branch January 17, 2026 03:55
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.

fix(ci): build-phar workflow not triggered by release-please

2 participants