Getting Started

Install with composer require vendor/package:^0.2 (replace vendor/package with the actual package name). This release is identical to 0.1 except that its Composer constraints now allow Symfony 3+ components.
First check your Laravel version: Laravel 5.4+ ships with Symfony 3, so 0.2.0 is the version to use. If you are on Laravel 5.3 or earlier (Symfony 2), stay on 0.1.x.
First use case: drop the package into a Laravel 5.4+ app and use its Symfony-backed functionality without hitting Composer dependency conflicts. No new API or configuration was added, so existing 0.1 usage patterns apply unchanged.

Implementation Patterns

Use the package exactly as you would in 0.1: register its service provider, publish any config if applicable, and resolve its classes via the container or facades.
When upgrading an existing app, run composer update vendor/package and confirm that no other dependency still pins Symfony 2. The only behavioural difference is the widened version constraint.
In CI, test against both Symfony 2 (using 0.1) and Symfony 3 (using 0.2) if you maintain a library that depends on this package. For application code, lock to ^0.2 only when your symfony/* packages are already on 3.x.
Because the release notes state “same with 0.1”, any integration tips, extension points, or customisations from 0.1 remain valid. There is no migration path beyond updating the version constraint.

Composer conflict: if another package requires Symfony 2, you cannot install 0.2.0. Run composer why symfony/symfony (or composer why symfony/console) to find the blocker.
The release is a compatibility-only change. Any bugs, missing features, or quirks present in 0.1 are still present in 0.2.0—do not expect fixes.
No deprecations or breaking changes were introduced. The public API is unchanged.
Debugging: use composer show vendor/package and composer show symfony/symfony to verify the installed versions. If you see a constraint error, check your composer.json for a direct or transitive symfony/* requirement pinned to ^2.
Tip: if you are not ready to move your whole app to Symfony 3, keep using 0.1.x. There is no reason to force 0.2.0 unless you need Symfony 3 compatibility.