Update dependency psr/link to v2

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
psr/link	require	major	^1.0 -> ^1.0 || ^2.0

---

Release Notes

php-fig/link

v2.0.1

Compare Source

Changed

• BREAKING The type of the $value parameter of EvolvableLinkInterface::withAttribute() was widened to comply with the original specification.

v2.0.0

Compare Source

Changed

• BREAKING All methods have return types

v1.1.1

Compare Source

v1.1.0

Compare Source

Changed

• All methods have typed parameters
• Bump required PHP version to 8.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

Read more information about the use of Renovate Bot within Laminas.

[internalsystemerror]

Looks like this is going to require dropping PHP 7.4 support to fix as the signature:

public function withLink(LinkInterface $link): self

needs to become

public function withLink(LinkInterface $link): static

and the static return return type doesn't exist until PHP 8.0. Testing out some of these fixes, it seems to support psr/link v2 might require BC breaks and so a new major release.

[Ocramius]

Since our symbols are not final, introducing psr/link:^2 compatibility means inheriting BC breaks.

We have 2 alternatives:

1. release 3.0.0 with psr/link:^1 and psr/link:^2 compatibility, then 4.0.0 with psr/link:^2 only
2. release 3.0.0 with psr/link:^2 and skip the transition completely

A lot of added final to the codebase would also help in avoiding this mess again.

[boesing]

I think introducing new majors in packages like this is fine.

There are only three dependents listed on packagist:
https://packagist.org/packages/mezzio/mezzio-hal/dependents?order_by=downloads

[Ocramius]

@boesing you mean "inheritance unlikely"? I'd still release a major for correctness then, but skipping v1 + v2 compat, and going straight for v2...

[boesing]

@Ocramius
No, I mean that components like this are usually not "used" that often (when we ignore actual "projects"). So its unlikely that there is another component out there using this component.
Usually, we are only talking about real projects and these projects can easily handle their upgrade paths on their own schedule.
When we bump majors as in laminas-servicemanager, we end up having to provide support for that in ~130 of our own components as well:
https://packagist.org/packages/laminas/laminas-servicemanager/dependents?query=laminas%2Flaminas-

But this component here is used in 0 of our own components and only a hand full of other components on packagist use this component at all.
So introducing 1 or more new major versions does not really introduce a high workload from what I can see.

[internalsystemerror]

OK, so to sum up, when I get the time again, I will update #59 to:

• Be a new major
• Drop support for psr/link v1

We would not be able to support both 1 and 2 from what I gathered when I was last looking at this due to the signature changes (happy to stand corrected if someone else figures out a way though). At least not without some intervention as to which class is loaded based on the PHP version or installed psr/link version.

[Ocramius]

Sounds reasonable: go for it whenever you want 👍

[Ocramius]

Closing here, since the @renovate noise is not helpful: #59 tackles this from a developer PoV.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 2.x releases. But if you manually upgrade to 2.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.