Chrome's behavior for how cookies are sent is changing. It's to be expected that other browser vendors will follow suit sooner or later:

• Tracking bug for Firefox

Sites that depend on cookies being sent cross-origin must add the attributes SameSite=None; Secure

Otherwise cookies without the SameSite attribute will be treated as if SameSite=Lax was set, meaning they will be restricted to first-party context.

Importing new releases from third-party sites utilizing release editor seeding is one of the most popular methods that will stop working properly.

There are already reports of disruptions in the workflow of multiple editors:
https://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/4552690/