Versioning Bundle Laravel Package

Product Decisions This Supports

• Feature Development: Enables seamless integration of semantic versioning into Symfony applications, allowing teams to display version numbers dynamically in UIs (e.g., admin dashboards, changelogs, or footer links) without manual updates.
• Roadmap Alignment: Supports compliance with Semantic Versioning (SemVer 2.0.0) for consistent release tracking, aligning with engineering best practices and reducing miscommunication in version-dependent workflows (e.g., API contracts, client updates).
• Build vs. Buy: Eliminates the need to build custom versioning logic from scratch, saving development time and reducing technical debt. Ideal for teams prioritizing maintainability over reinventing versioning systems.
• Use Cases:
  • User Transparency: Show version numbers in frontend/backend to build trust (e.g., "Powered by v1.2.3").
  • Debugging/Analytics: Log versions in error reports or usage analytics to correlate issues with specific releases.
  • CI/CD Integration: Automate version extraction from Git tags or Capistrano, ensuring consistency across deployments.
  • Multi-Environment Support: Differentiate versions for staging/production (e.g., 1.0.0-beta vs. 1.0.0).

When to Consider This Package

• Adopt if:

  • Your Symfony app lacks a standardized way to track versions across environments.
  • You need automated version detection (Git tags, Capistrano, or static files) to reduce manual errors.
  • Your team follows Semantic Versioning and wants to enforce it programmatically.
  • You require Twig integration for dynamic version display in templates (e.g., {{ app.version }}).
  • You’re open to extending version providers (e.g., adding support for GitLab CI variables or custom SCMs).

• Look elsewhere if:

  • You’re not using Symfony (this bundle is framework-specific).
  • You need advanced versioning features (e.g., pre-release suffixes, custom validation rules) beyond SemVer 2.0.0.
  • Your team prefers manual version control (e.g., hardcoded in config.php) over automated providers.
  • You require high maturity/stability: The package has low adoption (0 stars) and untested long-term usage.
  • You need versioning for non-Symfony PHP apps (consider standalone libraries like nikolaposa/version).

How to Pitch It (Stakeholders)

For Executives: "This package lets us automatically track and display our app’s version number—no manual updates needed. It’s a 10-minute setup that saves dev time, reduces errors, and gives us consistency for releases, support, and user transparency. For example, we could show ‘v1.2.3’ in the admin panel or log it with errors to debug faster. It’s low-risk (MIT license) and aligns with industry standards like Semantic Versioning."

For Engineering: "The versioning-bundle integrates seamlessly with Symfony to pull versions from Git tags, Capistrano, or static files—no more forgetting to update VERSION constants. It exposes the version as a Twig global ({{ app.version }}), so we can use it anywhere. We can also extend it for custom providers (e.g., GitLab CI). The tradeoff? It’s Symfony-only, but if we’re already using the framework, this is a no-brainer for consistency and automation."