Repository navigation
feat: rename the package to roadrunner/worker - #53
Conversation
build: depend on roadrunner/* packages chore: polish composer.json metadata The package keeps its version line and replaces spiral/roadrunner-worker with self.version, so packages that still require spiral/roadrunner-worker are satisfied by roadrunner/worker and both names never get installed together. Version::current() looks up roadrunner/worker before the old name, because the replaced entry carries no pretty version. Namespaces stay unchanged. Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to The package rename and dependency update show no concrete merge-blocking issue in the reviewed changes. Pre-merge checks |
|
What was changed
roadrunner/workerand replacesspiral/roadrunner-workerwithself.version; namespaces stay unchanged.roadrunner/goridge ^4.5;suggestpoints toroadrunner/cli.Version::current()checksroadrunner/workerbefore the old name: the replaced entry inInstalledVersionshas no pretty version.Why?
The roadrunner-php packages move to the
roadrunner/vendor;roadrunner/goridge4.5.0 is already released the same way. The new name has to be registered on Packagist before release.Checklist
composer validate --strict, testo (90 tests) and psalm pass locallySummary by CodeRabbit
roadrunner/workeracross installation guidance and package metadata. The previous package name is recognized as replaced.roadrunner/goridge ^4.5, and the suggested CLI package is nowroadrunner/cli.