Sonnar can't find release - year in the name

Sonarr version (exact version):
Mono version (if Sonarr is not running on Windows):
OS: Docker@Debian
Debug logs:
2022-11-24 09:06:14.7|Debug|Parser|Parsing string ‘Kuchenne rewolucje [2022] [S25E13] MULTI.POLISH [720p] [WEB-DL-CZRG] [x264]’
2022-11-24 09:06:14.7|Debug|Parser|Episode Parsed. Kuchenne rewolucje [2022] - S25E13
2022-11-24 09:06:14.7|Debug|Parser|Language parsed: Polish
2022-11-24 09:06:14.7|Debug|QualityParser|Trying to parse quality for Kuchenne rewolucje [2022] [S25E13] MULTI.POLISH [720p] [WEB-DL-CZRG] [x264]
2022-11-24 09:06:14.7|Debug|Parser|Quality parsed: WEBDL-720p v1
2022-11-24 09:06:14.7|Debug|Parser|Release Group parsed: x264
2022-11-24 09:06:14.7|Debug|ParsingService|No matching series Kuchenne rewolucje [2022]
2022-11-24 09:06:14.7|Debug|DownloadDecisionMaker|Release rejected for the following reasons: [Permanent] Unknown Series

Description of issue:
On few of my private trackers, there is problem that each series has a year in a name of the release (after the name of the series). Unfortunately SONNAR each position from this site parse wrongly, treat the year as a part of the series name and can’t match it the the series which I need.
Is is possible modify if somewhere in options to avoid this?
Name of release: ‘Kuchenne rewolucje [2022] [S25E13] MULTI.POLISH [720p] [WEB-DL-CZRG] [x264]’
Sonnar parse it: Kuchenne rewolucje [2022] - S25E13
Result after that: Release rejected for the following reasons: [Permanent] Unknown Series

Request a mapping

Already did it, but it has been refused with info as below:

11/9/2022 4:08:47 208351 Kuchenne Rewolucje [2022] Kuchenne Rewolucje [2022] is example, in general name of the episodes on some tracker contains year and Sonnar treat this year as part of series name Need full release names

BTW: It’s not a solution as on those 2 trackers, EACH series are names this way, so in this case I have to request for everything I want to download using sonnar and also with each year (for instance Kuchenne Rewolucje [2022], Kuchenne Rewolucje [2021], etc.) Am I right?
Is there no option to just modify it locally on my instance?

OK, so it was refused because you did not provide the information as requested. You can resubmit and this time provide the information.

This is the solution, it is why it exists. It is because your trackers and/or release groups are using non-standard naming conventions. Conventions exist for a reason. If they change the year for each new season then yes, you will need to request a separate mapping for each variant.

To my knowledge there is no way to modify it locally. You either have to process everything manually, or have a mapping created so the automation will work.

Trackers like those really need to stop trying to reinvent naming, that said this format is almost supported as-is, but the year in square brackets is a little bit of a wrench in the system.

I’ve pushed a fix for this that will be in the v4 beta soon, no aliases required.

And to answer your question from the alias form, no you can’t just ignore years.

I know it’s not the best practise of them, but they have a lot of FL positions that’s why I prefer them as 1st and 2nd choice.
I downloaded today, after read info from Excel new v4 version from docker (linuxserver) but it didn’t help - I assume that it’s not still done and will be available soon?

thanks in advance!