Releaser Laravel Package

Product Decisions This Supports

• Automating Release Workflows: Streamlines version bumping, changelog generation, and release tagging for open-source projects adhering to Semantic Versioning, reducing manual effort and human error. The new --no-signing option adds flexibility for teams that do not require GPG-signed tags, broadening adoption for projects with varying security needs.
• Developer Experience (DX) Improvements: Enables teams to focus on features rather than release logistics, particularly for smaller projects or solo maintainers. The optional signing toggle simplifies onboarding for teams without GPG infrastructure.
• Consistency in Open-Source Releases: Ensures adherence to best practices (e.g., versioning, changelogs) without requiring custom scripts or complex tooling. The new option aligns with modern workflows where signing may not be mandatory.
• Build vs. Buy Decision: A lightweight, MIT-licensed alternative to commercial tools (e.g., GitHub Releases, GitLab CI/CD) or heavier frameworks (e.g., custom PHP scripts) for teams prioritizing simplicity and flexibility.
• Roadmap Alignment: Ideal for projects planning to adopt Semantic Versioning or needing to standardize release processes early in development. The optional signing feature supports incremental adoption of security practices.

When to Consider This Package

• Adopt if:

  • Your project follows or plans to adopt Semantic Versioning and lacks a standardized release process.
  • You’re a small team or solo maintainer managing open-source PHP/Laravel projects and want to avoid reinventing release workflows.
  • You prefer lightweight, dependency-minimal tools over heavy CI/CD pipelines or commercial solutions.
  • Your team values MIT-licensed, self-hosted control over cloud-based release tools (e.g., GitHub/GitLab native features).
  • You’re comfortable with PHP-based tooling and don’t need integrations with modern DevOps tools (e.g., Slack, Jira).
  • You do not require GPG-signed tags (now optional with --no-signing) or want to disable signing for specific releases.

• Look Elsewhere if:

  • Your project uses non-PHP ecosystems (e.g., Node.js, Python) or requires multi-language support.
  • You need advanced release features (e.g., automated changelog generation from PRs, pre-release checks, or Docker image publishing).
  • Your team relies on GitHub/GitLab’s native release tools or prefers GitHub Actions/GitLab CI for workflows.
  • You require active maintenance (last release: 2019) or modern PHP 8.x compatibility (package may lag).
  • Your project has complex release cycles (e.g., multi-repo dependencies, canary releases) or mandatory GPG signing requirements.

How to Pitch It (Stakeholders)

For Executives/Stakeholders: "This package automates semantic versioning releases for our open-source PHP/Laravel projects, saving dev time and reducing errors. By adopting Releaser, we standardize our release process—bumping versions, generating changelogs, and tagging releases—with minimal overhead. The new --no-signing option adds flexibility for teams without GPG infrastructure, making it easier to adopt. It’s a lightweight, self-hosted alternative to GitHub/GitLab’s native tools, ideal for small teams prioritizing simplicity and control. The MIT license ensures no vendor lock-in, and it aligns with our roadmap for Semantic Versioning. Trade-off: Limited modern maintenance, but perfect for our current needs."

For Engineering: *"Releaser is a PHP CLI tool to automate Semantic Versioning releases for our Laravel/open-source projects. Key benefits:

• Reduces release drudgery: Handles version bumps (major, minor, patch), changelog updates, and Git tags in one command.
• Lightweight: No heavy dependencies; just a Composer package.
• Self-contained: Works offline or in CI (e.g., GitHub Actions) without external APIs.
• Customizable: Supports hooks for pre/post-release tasks (e.g., notifications) and now includes --no-signing to skip GPG tag verification if needed.

Use case: Replace manual git tag + composer version workflows. Not ideal if you need deep CI integrations, PHP 8.x support, or mandatory GPG signing—consider GitHub Actions or GitLab CI instead. Let’s prototype it for our next minor release, especially if we want to skip signing for internal pre-releases!"*