ddd-composer-update-version

To automate composer version bumps, this Skill updates the composer.json version, commits the change, and creates a git tag to trigger Packagist updates. It handles the complete release workflow from version increment to repository tagging.

Yes, you can use this composer versioning workflow in a monorepo. It automates version bumps across a repository with multiple packages and supports non-linear release workflows for core packages and modules.

To trigger Packagist updates with a git tag, you need a clean working tree, access to push to the repository, and a CI pipeline to publish the tag to Packagist. The tag name must match the composer.json version.

Your composer release tag fails to update Packagist if tag names do not match the composer.json versions. Ensuring tag names match the composer.json versions is required for successful Packagist releases and updates.

The best way to manage composer versioning across multiple packages is automating the bump, commit, push, and tag sequence. This ensures consistent tag names matching composer.json versions to reliably trigger Packagist releases.