v1.3.8 not published to unity package manager

[delphinius81]

While v1.3.8 has been tagged and released in github, it was not published into unity's package manager. Is there an update on timing for this?

Current workaround is to pin to the github tag, but that doesn't work when trying to have livekit as a custom package dependency.

[MaxHeimbrock]

Thanks for reporting, I will have a look.

[MaxHeimbrock]

I can not confirm. I use this line in my manifest:
"io.livekit.livekit-sdk": "git@github.com:livekit/client-sdk-unity.git",
and I get v1.3.8

Can you try again?

[delphinius81]

Right, because you are pointing directly to the github repo. If you try to just point to a specific version number, via "io.livekit.livekit-sdk": "1.3.8", it will not be found. The release was only published to git, and not to OpenUPM.

[MaxHeimbrock]

I see, you are probably using OpenUPM as an additional package registry right? On their library I can also see that v1.3.7 is the latest version there: https://openupm.com/packages/io.livekit.livekit-sdk/

According to OpenUPM, they should get notified about our releases and pull the latest into their registry automatically. In this case, I am unsure if something went wrong, but I will investigate.

Could you confirm that you are using the OpenUPM registry?

[MaxHeimbrock]

I can see the issue on the OpenUPM build pipeline: https://openupm.com/packages/io.livekit.livekit-sdk/?subPage=pipelines

E901 heap out of memory

Might be our binary plugins are too large for OpenUPM to handle.

[delphinius81]

Correct, I'm using OpenUPM.

We've had this issue with other custom packages we own. We ended up having to switch to releases via git tag due to their total size.