Bump composer/installers constraint from ~1.0 to ^1 || ^2 in module packages

[Samuell1]

Summary

The OctoberCMS module packages (october/backend, october/cms, october/dashboard, october/media, october/system) currently require composer/installers: ~1.0, which pins the dependency to v1.x.

Meanwhile, october/rain already accepts ^1 || ^2, so the library is ready for v2 but the module packages are holding it back.

Affected Packages

Package	Current Constraint	Suggested Constraint
october/backend	~1.0	^1 || ^2
october/cms	~1.0	^1 || ^2
october/dashboard	~1.0	^1 || ^2
october/media	~1.0	^1 || ^2
october/system	~1.0	^1 || ^2
october/rain	^1 || ^2	✅ Already updated

Why

composer/installers v2.x has been stable since 2022. The ~1.0 constraint prevents projects from using v2, which brings improvements and is the version recommended by Composer. Since october/rain already supports both versions, aligning the module packages would allow the ecosystem to move forward.

Environment

• OctoberCMS v4.1.17
• PHP 8.4
• Laravel 12

[daftspunk]

Thanks for reporting this. Since october/rain includes it now, all packages and modules can omit this entirely. We'll remove it from the modules in the next patch.