New neoforge versions causing issues - Pin beta version to fix?

[Adavee]

Apologies if this is not the right way to handle issues in here. I have accumulated some issues/questions the last couple of days.

Mainly: How can I pin a beta version of Neoforge? I had things working nicely on 21.6.12-beta, but I've had to restart the container a couple of times recently and each time it grabs a new version of Neoforge. Versions .19 and .20 have caused a couple of issues and I don't know how to revert back to .12. If I can't use a direct version value in the yaml file, can I at least pass a flag to prevent downloading new modloader versions once I've got one that works?
docker-compose.txt
(I've removed usernames and location identifiers from attachments for privacy)

The issues I've encountered are:
Issue 1: Random client time-outs. Started after moving from .12 to .19, but I don't know if this is coincidence as I can't understand the cause.
Time-out issue Client-side Exception.txt
Time-out issue Server-side log entries.txt

Issue 2: After having a lot of connection time-outs, per Issue 1, I decided to restart the container again. This bumped it to .20 but now it won't start at all.
Launch crash issue Crash log.txt

I'm guessing these are neoforge issues, rather than docker or image issues, but it helps explain why I'd want to be able to control beta versions.

[Adavee]

I've solved this question with support from the Neoforge team and some trial and error. It's as simple as entering the version variable without the -beta suffix. Eg. NEOFORGE_VERSION: 21.6.12 instead of NEOFORGE_VERSION: 21.6.12-beta

Neoforge support indicated there are currently compatibility issues between the Xaero's minimap mod and the current Neoforge version. Not sure when those will be resolved, or by whom.