@metabase/rde 0.5.0 → 0.5.1

package/README.md

@@ -152,7 +152,7 @@ Docker is used whenever it is available: the image is self-contained, and the co
 
 rde runs Metabase Enterprise 65 or newer. Once Metabase is up, `rde init`, `rde start`, and `rde upgrade` read the version it reports and refuse the OSS edition (a `v0.…` version, which `metabase/metabase` runs), a release before 65, and a build of master (a `-SNAPSHOT` version, which `metabase/metabase-enterprise-head` runs), with exit code 2 and the way to another: `rde upgrade --to <image or release tag>` for this instance, or `rde uninstall`, then `rde init --image <image>` or `rde init --jar <release tag>`, for a new one. The refused instance is left running as it is. `--jar` refuses a `v0.…` tag before anything is downloaded. With `RDE_DEV=1`, for working on rde and Metabase themselves, every version runs.
 
-A new instance runs the newest release that Metabase's release feed (`https://static.metabase.com/version-info-ee.json`) lists of Enterprise 65 or newer, betas and release candidates left out. The feed's own `latest`, like the Docker `:latest` tag, moves to a new major only weeks after its release, so rde reads neither. Docker gets the major line of that release, `metabase/metabase-enterprise:v1.<major>.x`, a tag Metabase moves to every build of the major: the state file records the line, and each pull of it brings the newest build. The jar gets the release itself. While the feed lists no release of 65 or newer, `init` stops with exit code 2 before it pulls or downloads anything, and names the ways out: `--image <image>`, `--jar <release tag>`, or `RDE_DEV=1` for the development build. When the feed cannot be read, `init` stops the same way, with the cause and `--image <image>` or `--jar <release tag>` as the way past it. In development mode the image is `metabase/metabase-enterprise-head:latest`, and the jar's `latest` is the feed's own `latest`.
+A new instance runs the newest release that Metabase's release feed (`https://static.metabase.com/version-info-ee.json`) lists of Enterprise 65 or newer, a beta included: a major's betas are its `.0` builds and its first final release is `.1`, so a beta runs only until that final is out. The feed's own `latest`, like the Docker `:latest` tag, moves to a new major only weeks after its release, so rde reads neither. Docker gets the major line of that release, `metabase/metabase-enterprise:v1.<major>.x`, a tag Metabase moves to every build of the major: the state file records the line, and each pull of it brings the newest build. The jar gets the release itself. While the feed lists no release of 65 or newer, `init` stops with exit code 2 before it pulls or downloads anything, and names the ways out: `--image <image>`, `--jar <release tag>`, or `RDE_DEV=1` for the development build. When the feed cannot be read, `init` stops the same way, with the cause and `--image <image>` or `--jar <release tag>` as the way past it. In development mode the image is `metabase/metabase-enterprise-head:latest`, and the jar's `latest` is the feed's own `latest`.
 
 ## Everyday commands
 

package/dist/cli.mjs

@@ -2243,7 +2243,6 @@ const VERSION_INFO_PATH = "/version-info-ee.json";
 const JAR_FILE = "metabase.jar";
 const RELEASE_TAG$1 = /^v(?<edition>[01])\.(?<major>\d+)\.\d+(?:\.\d+)?(?:-[\w.]+)?$/;
 const MAJOR_LINE_TAG = /^v(?<edition>[01])\.(?<major>\d+)\.x$/;
-const FINAL_ENTERPRISE_RELEASE = /^v1\.\d+\.\d+(?:\.\d+)?$/;
 const ENTERPRISE_EDITION = "1";
 const OPEN_SOURCE_EDITION = "0";
 const SNAPSHOT_SUFFIX = "-SNAPSHOT";
@@ -2282,11 +2281,13 @@ function compareReleases(left, right) {
 	return 0;
 }
 function supportedRelease(version) {
-	if (!FINAL_ENTERPRISE_RELEASE.test(version)) return null;
-	const major = releaseMajor(version);
-	return major !== null && major >= 65 ? {
+	const groups = RELEASE_TAG$1.exec(version)?.groups;
+	const major = groups?.["major"];
+	if (groups?.["edition"] !== ENTERPRISE_EDITION || major === void 0) return null;
+	const number = Number.parseInt(major, 10);
+	return number >= 65 ? {
 		version,
-		major
+		major: number
 	} : null;
 }
 function newestSupportedRelease(versions) {
@@ -9373,7 +9374,7 @@ const db = defineCommand({
 //#endregion
 //#region package.json
 var name = "@metabase/rde";
-var version = "0.5.0";
+var version = "0.5.1";
 var description = "Prepares a local machine for data-engineering work with Metabase and coding agents";
 //#endregion
 //#region src/version.ts

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@metabase/rde",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "Prepares a local machine for data-engineering work with Metabase and coding agents",
   "keywords": [
     "analytics",