Any chance of tagging some of the more up-to-date changes?

[GuySartorelli]

The last tag on this repository (and consequently in packagist) was 3 years ago.
There have been some important changes since then - for example PHP 8.4 support.

Is there any chance this package will get a new tag in the near future so we can use the latest changes in projects without relying on potentially unstable constraints?

[k00ni]

You might have seen #113, a rather big PR which brings full PHP 8 support up to PHP 8.5. I hope @lanthaler finds the time to give feedback before Christmas.

It would be great if you could give it a try and get back to me if you found issues.

JSON-LD is used in my EasyRdf fork https://github.com/sweetrdf/easyrdf, but I am planning to switch to my own JSON-LD fork if #113 becomes stale: https://github.com/sweetrdf/json-ld. This might be an option for you in case there is no reaction from the author (anytime soon),

[GuySartorelli]

It would be great if you could give it a try and get back to me if you found issues.

I'll try to carve out some time to try it out next week, though I make no promises and my usage will be very limited since I don't use this library directly.

In any case while PHP 8.5 support is great, merging that PR shouldn't be a blocker for tagging the PHP 8.4 support that has already been merged in.

This might be an option for you in case there is no reaction from the author (anytime soon)

Unfortunately I don't use this library directly - it's a dependency of a dependency, so my options in that regard are limited 😅

Unless you are intending to use the replace property in your fork's composer.json file if it does come to that? That way for scenarios like mine we could declare your fork as a dependency which (if I understand replace correctly) means it would be used instead of this one?

[GuySartorelli]

@k00ni Turns out my colleague already tried your fork so I'll skip trying it myself. Sounds like your fork resolves the deprecation warnings we had seen and doesn't have any obvious regressions or bad effects for our (admittedly limited) use case.