Why are old versions unavailable?

[mnahkies]

I went to do some work on an old project today, and found that my yarn install was failing. Looking at the logs it's because the atlas version no longer exists.

# This file contains the result of Yarn building a package (@ariga/atlas@npm:0.21.1)
# Script name: preinstall

The specified Atlas version does not exist or is no longer supported.
node:internal/errors:983
  const err = new Error(message);
              ^

Error: Command failed: ./install.sh --no-install --output ./atlas --platform linux-amd64 -y --user-agent atlas-npm
    at genericNodeError (node:internal/errors:983:15)
    at wrappedFn (node:internal/errors:537:14)
    at checkExecSyncError (node:child_process:882:11)
    at execFileSync (node:child_process:918:15)

This feels like a bit of a rug pull - I can understand not providing support for older versions, but removing them completely and breaking existing projects doesn't feel great.

In this instance upgrading to the latest version was straight forward, but that might not always be true. For something as critical to a project as database migrations, I don't want to find myself forced into a surprise migration.

[giautm]

Hey, it's our policy for distributed binary, to keep the user using latest version of atlas with bugs fixed. See: https://atlasgo.io/cli-reference#distributed-binaries

[icopp]

This is a bad policy. The versions after 0.32 have broken preexisting schemas for my company and we have no decent way to troubleshoot it yet, so if that version gets pulled our only resort will be to abandon Atlas completely.

[a8m]

We disabled binary deletion job a few weeks ago after getting feedback from several customers. However, we still recommend sticking to the latest versions, as we actively fix bugs and security issues.

... so if that version gets pulled our only resort will be to abandon Atlas completely.

I can't help much without reproducing the issue (I tried multiple times without luck), but I really want to help. Please contact us on Intercom or Discord. I'll need your schema and config file to reproduce this, and they'll be deleted after we identify the issue.