Version Bundle Laravel Package

Product Decisions This Supports

• Versioning Strategy Standardization: Enables a consistent, automated approach to version management across Symfony2/Laravel applications, reducing manual errors and ensuring alignment with semantic versioning (e.g., MAJOR.MINOR.PATCH).
• Roadmap for CI/CD Integration: Simplifies version bumping in pipelines (e.g., post-release, pre-deployment hooks) by providing a CLI command (corley:version:bump), reducing friction in automated workflows.
• Build vs. Buy Decision: Justifies buying this lightweight solution over custom scripts or reinventing versioning logic, especially for teams already using Symfony2/Laravel.
• Use Cases:
  • Internal Tools: Track versions of admin panels, APIs, or microservices.
  • Customer-Facing Apps: Display version numbers in footers (e.g., v1.2.3) for transparency or support debugging.
  • Static Asset Caching: Append version hashes to filenames (e.g., styles.css?v1.2.3) to bypass browser caching during updates.
  • Release Notes Automation: Integrate with changelog tools by storing version metadata in version.yml.

When to Consider This Package

• Adopt When:
  • Your team uses Symfony2/Laravel and lacks a standardized versioning system.
  • You need CLI-driven version bumps (e.g., tied to Git tags or release workflows).
  • You want to embed version numbers in templates or static assets without manual updates.
  • Your project is small-to-medium (low maintenance overhead; no complex versioning needs like multi-repo dependencies).
• Look Elsewhere If:
  • You’re using Laravel 5.5+ (prefer native composer version or packages like laravel-version).
  • You need advanced versioning (e.g., pre-release tags, build metadata, or multi-package coordination).
  • Your stack is not Symfony2/Laravel (e.g., Node.js, Go, or non-PHP backends).
  • You require enterprise-grade support (this package has minimal adoption; consider commercial alternatives like SemVer tools or GitHub Actions).
  • You’re already using a dedicated package manager (e.g., semver in Node.js) that handles versioning globally.

How to Pitch It (Stakeholders)

For Executives: "This package automates version management for our Symfony2/Laravel apps, saving dev time and reducing errors. With a single CLI command (corley:version:bump), we can update versions consistently—critical for releases, support, and customer transparency. It’s lightweight, open-source, and integrates seamlessly with our existing stack. For ~$0 cost, we gain reliability and scalability for versioning across all products."

For Engineers: *"Need a drop-in solution for versioning in Symfony2? This bundle:

• Bumps versions via CLI (no manual edits to composer.json or files).
• Stores versions in config/version.yml (version-controlled, easy to audit).
• Exposes versions in Twig (e.g., footers, asset hashing) with zero boilerplate.
• Works with semantic versioning out of the box. Perfect for internal tools, APIs, or apps where version visibility matters. Let’s prototype it in [Project X]—it’s a 10-minute setup."

For Developers: *"If you’re tired of forgetting to update version numbers or dealing with merge conflicts in composer.json, this bundle handles it for you:

# Bump version
php app/console corley:version:bump 1.0.0

# Display current version
php app/console corley:version:show

# Use in Twig:
{{ version.number }}  # Renders '1.0.0'

No dependencies, no complexity—just reliable versioning. Try it in your next feature branch!"