Container downloading latest RELEASE verison instead of PREVIEW, despite env VERSION: PREVIEW

[fultonm]

My docker compose file has been working for years to keep Preview version up to date. But this morning, I noticed it downloaded and deployed 1.21.84.1 which I assume is the latest Release version instead of latest Preview version. It seems this behavior change aligns with checking in this PR: itzg/mc-bds-helper#1

# location of this compose file.

version: '3.4'

services:
  bds:
    image: itzg/minecraft-bedrock-server
    restart: unless-stopped
    environment:
      VERSION: PREVIEW
      EULA: "TRUE"
    ports:
      - 19132:19132/udp
    volumes:
      - ./data:/data
    stdin_open: true
    tty: true```

[fultonm]

Update: I built the container from this repo and having the same issue still

[itzg]

Yep will be working on a follow up to #525 which was a first round fix to deal with Mojang breaking the existing automation.

[fultonm]

Yep will be working on a follow up to #525 which was a first round fix to deal with Mojang breaking the existing automation.

I see thanks for the update

Due to this issue, the server downgraded to a previous version and that has corrupted the world files. We have backups, but upon restoring back ups, it seems that there is some more corruption that was automatically repaired. things are working OK now. but I am worried about corruption long-term.

Is there ever a circumstance where a downgrade server version is expected? If not, can the container block a downgrade, unless there’s some specific config allowing that?

[itzg]

I'm sorry for that unexpected downgrade, but no I don't think Mojang would ever release a version downgrade. This case was artificially induced by the change in image automation logic.

I'll give some thought to guard against that.

Sure would be nice if the bedrock software itself detected a downgrade and didn't just blindly corrupt world data.