Weave Code
Releaser Laravel Package
woohoolabs/releaser
Lightweight CLI release tool for open-source projects. Runs in a Git repository to bump SemVer versions and create signed Git tags (GPG). Install via Composer and execute ./vendor/bin/releaser to publish a new release.
Woohoo Labs. Releaser is a lightweight release tool for Open Source projects following semantic versioning.
Frequently asked questions about Releaser
- Can I use woohoolabs/releaser for Laravel package development?
- This package is CLI-focused and doesn’t integrate natively with Laravel. You’d need to wrap it in an Artisan command or custom script. For Laravel-native solutions, consider spatie/laravel-release or laravel-package-tools instead.
- How do I install and run releaser in a Laravel project?
- Run `composer require woohoolabs/releaser`, then execute `./vendor/bin/releaser` from your project root. Ensure you’re in a Git repo with GPG set up, as the tool signs tags by default. For Laravel, pair it with a custom Artisan command for seamless integration.
- Does this package support PHP 8.x or 9.x?
- No evidence suggests compatibility with PHP 8.x/9.x. The last update was in 2019, and no modern PHP features (e.g., named arguments) are supported. Test thoroughly or use alternatives like php-semver for newer PHP versions.
- How do I skip GPG signing for internal releases?
- Use the `--no-signing` flag, e.g., `./vendor/bin/releaser --no-signing`. This is useful for CI/CD pipelines or internal projects where GPG isn’t required. Note: Unsigned tags may weaken release integrity for open-source projects.
- Will this work with Laravel’s database migrations?
- No, this package doesn’t handle migrations. You’ll need to manually sync version bumps with your `migrations` table or use tools like laravel-migrations-generator alongside it.
- Is there a Laravel-specific alternative to this package?
- Yes. For Laravel, prioritize `spatie/laravel-release` (native Artisan commands) or `laravel-package-tools` (comprehensive package scaffolding). These integrate with Laravel’s ecosystem better than a generic CLI tool.
- How do I automate releases in CI/CD with this tool?
- Add the releaser command to your CI pipeline (e.g., GitHub Actions). Use `--no-signing` if GPG isn’t needed, but ensure your pipeline still enforces release integrity via other means (e.g., GitHub/GitLab release APIs).
- What happens if GPG isn’t configured but I don’t use --no-signing?
- The tool will fail with a GPG error. Always test locally first or use `--no-signing` to bypass signing. For CI/CD, ensure GPG keys are available or disable signing if unnecessary.
- Can I use this for monorepos or multi-package projects?
- No. This package targets single-repo workflows. For monorepos, consider `monorepo-builder` or custom scripts combining `php-semver` with Git tagging logic.
- What’s the maintenance status of this package?
- Last updated in 2019 with minimal activity. No PHP 8.x/9.x support or recent Composer plugin updates. Use at your own risk or fork it for critical projects. Alternatives like `spatie/laravel-release` are actively maintained.
Weaver
How can I help you explore Laravel packages today?