Whenever obs-websocket releases a new minor version, the client library is auto generated, but if the minor version has new requests, the tests will fail because we're testing against the older version of the server, e.g. https://github.com/andreykaipov/goobs/pull/131
Since obs-websocket is bundled with OBS now, this PR gets the latest artifact from obsproject/obs-studio's push workflow and uses that instead of the PPA because it could be weeks until it's updated.
It also builds the image before bumping instead of on a weekly cadence. Hopefully the next time there's a minor version bump with new requests, this will automatically build the image, the generated protocol PR will be created, and the tests can pass.
This PR also changes the retention policy on our ghcr images (TBD). No need to do this as I only remove untagged images.
Whenever obs-websocket releases a new minor version, the client library is auto generated, but if the minor version has new requests, the tests will fail because we're testing against the older version of the server, e.g. https://github.com/andreykaipov/goobs/pull/131
Since obs-websocket is bundled with OBS now, this PR gets the latest artifact from obsproject/obs-studio's push workflow and uses that instead of the PPA because it could be weeks until it's updated.
It also builds the image before bumping instead of on a weekly cadence. Hopefully the next time there's a minor version bump with new requests, this will automatically build the image, the generated protocol PR will be created, and the tests can pass.
This PR also changes the retention policy on our ghcr images (TBD).No need to do this as I only remove untagged images.