fix: add missing release fields to UserListensMBIDMapping

[RustyNova016]

Those fields are missing in the model structs.

[InputUsername]

Thanks @RustyNova016!

@shymega LGTM, feel free to merge.

[InputUsername]

Thanks @RustyNova016!

[shymega]

Sorry - my GitHub notifications page is reaching around 4 pages now, and possibly more - perhaps we could look into Mergify, or auto-merge queues, so we can approve a PR, and merge it once CI passes?

[InputUsername]

Sorry - my GitHub notifications page is reaching around 4 pages now, and possibly more - perhaps we could look into Mergify, or auto-merge queues, so we can approve a PR, and merge it once CI passes?

No worries, this one is on me actually. For some reason I assumed I had reviewed and needed your approval as well, but apparently PRs only need one approval. In the future I'll just merge smaller PRs myself (and feel free to do so yourself as well).

Never heard of Mergify so I'll look into that. I believe auto-merge queues are only available for repos under an organization or for Enterprise users. But honestly not sure if it's worth it in the first place, we don't get that many PRs.

[RustyNova016]

Mergify, or auto-merge queues, so we can approve a PR, and merge it once CI passes?

GitHub has a native way to do that.
You need to allow auto merge on the repo's settings, and it will automerge when CI pass, allongside branch protections

[shymega]

Yeah, that works too. We should definitely look into it - could even automate releases, but I'm not sure how comfortable I am with that.

@InputUsername Should I open a tracking issue for auto-merge queues?

[InputUsername]

@shymega I've enabled auto-merge, that should be enough right? I don't think we need more advanced functionality given the (relatively) low volume of PRs.