A beta is a release of the next version that is published before the stable release, so that you can test an application and a datastore against it. The install script and surreal upgrade stay on the current stable release unless you ask for the beta, and the Docker latest tag points to the stable release too.
--beta and db@beta install the most recent beta. After a version's stable release and before the first beta of the next one, the most recent beta is older than the stable release. Check the version that surreal version reports, and if it is older than the stable release, install the stable release instead, as described in Installation.
A new major version can convert an existing datastore to a new format that the previous version cannot open. For example, starting a 4.0 node on a 3.x datastore converts it to the 4.0 record format. Test a beta on a new datastore or on a copy, and read the upgrade guide for that version, such as Upgrading from 3.x to 4.0, before you start it on existing data.
Installing the beta on macOS and Linux
The install script installs surreal and the latest beta database, and pins it as the default.
curl --proto '=https' --tlsv1.2 -sSf https://install.surrealdb.com | sh -s -- --betaInstalling the beta on Windows
& ([scriptblock]::Create((irm https://windows.surrealdb.com))) -BetaUpgrading an installed database to the beta
With surreal already installed, upgrade the database component to the latest beta. The --beta flag is shorthand for db@beta.
surreal upgrade --betasurreal upgrade db@betaTo run one command against the beta without changing the default, use +beta, as in surreal +beta db start. See Managing components.
Using the beta with Docker
Docker Hub has no tag that follows the latest beta, so name the beta release in the tag. The tags are listed on Docker Hub. For example, the 4.0 beta was tagged v4.0.0-beta.1:
docker run --rm --pull always -p 8000:8000 surrealdb/surrealdb:v4.0.0-beta.1 start