Parameter Encryption Phpseclib Bundle Laravel Package

Product Decisions This Supports

• Framework upgrade planning: v1.1.0 adds Symfony 4.x support, which widens the compatible dependency window for Laravel applications on newer Symfony component versions. This directly informs decisions about when the product can move off older Laravel/Symfony baselines without forking or patching the package.
• Build vs. buy / adopt vs. maintain: If your roadmap includes upgrading framework major versions this year, this release reduces the "we'll have to maintain a fork" risk that often tips a build-vs-buy decision toward building in-house.
• Roadmap sequencing for platform work: Symfony 4.x support is an enablement item, not a customer-facing feature. Use it to sequence internal upgrade work (e.g., schedule the Laravel/Symfony bump after this version is pinned) rather than as a standalone roadmap line.
• Dependency and security posture: The removal of PHP CS Fixer and PHPUnit dist config files from git exports is packaging hygiene only — it does not change runtime behavior, but it does mean exported archives are leaner and less likely to ship stale tooling configs into downstream builds.
• Vendor risk tracking: A minor release that expands framework compatibility is a positive maintenance signal. It supports the argument that the package is actively maintained and worth keeping in the dependency inventory rather than replacing.

When to Consider This Package

Adopt or upgrade when:

• Your application depends on this package's functionality and you are planning or currently executing a move to Symfony 4.x-era components (or the corresponding Laravel version range). v1.1.0 is the minimum version that covers that combination.
• You are standardizing dependency versions across multiple Laravel services and need a single package version that spans your current and target framework versions.
• You package or vendor your dependencies (git exports, artifact builds) and want cleaner distributable archives without dev-tool configs.

Look elsewhere or defer when:

• You are pinned to an older Symfony/Laravel line and have no near-term upgrade plans — v1.1.0 offers no functional benefit, and staying on the prior version reduces change surface.
• You need a documented migration guide: this release provides none, and Symfony major-version support changes can surface transitive dependency conflicts. Validate in a staging branch before committing to the upgrade.
• Your decision hinges on runtime features or performance — this release adds compatibility, not capability. If the package's core functionality does not fit your use case, framework support is irrelevant.
• The package is a transitive dependency you do not control; in that case the practical action is pinning and monitoring, not evaluating adoption.

How to Pitch It (Stakeholders)

To executives: This is a maintenance release that keeps the package compatible with the newer Symfony 4.x framework line. It removes a blocker to planned framework upgrades and is a positive signal that the dependency is actively maintained. No customer-facing change, no migration cost expected, low risk.

To engineering: v1.1.0 adds Symfony 4.x support and strips PHP CS Fixer and PHPUnit dist configs from git exports. No breaking changes, no API changes, no deprecations. Action: bump the constraint, run the full test suite and a staging deploy, and confirm no transitive dependency conflicts from the widened Symfony range. Budget a short validation window rather than a migration project.

Recommendation: Upgrade on the next scheduled dependency maintenance pass, gated on a clean staging build. Do not treat it as a standalone initiative.