@the-meridian/cli 0.1.0 → 1.0.1

package/CHANGELOG.md

@@ -0,0 +1,13 @@
+# @the-meridian/cli
+
+## 1.0.1
+
+### Patch Changes
+
+- 628f7b4: Correct the `dev_database_limit_reached` hint. Development databases are now counted per collaborator, so the only way to hit that refusal is a plan with no development-database allowance at all. The hint no longer tells you to ask whoever owns the existing database to delete it, and points at the organization's plan instead.
+
+## 1.0.0
+
+### Major Changes
+
+- d24e50d: Initial public release of the Meridian CLI on npm, published via the changesets release pipeline.

package/dist/index.js

@@ -452,7 +452,7 @@ function extractErrorCode(body) {
   return record !== void 0 && typeof record.error === "string" ? record.error : void 0;
 }
 var HINTS_BY_ERROR_CODE = {
-  dev_database_limit_reached: "This app has reached its allowance of development databases. Whoever owns the existing one can delete it, or an organization owner/admin can remove it from the Meridian dashboard.",
+  dev_database_limit_reached: "Your plan does not include a development database for you on this app. Every collaborator gets their own out of the plan's allowance, so upgrading the organization's plan in the Meridian dashboard is what unlocks it.",
   dev_database_over_storage_limit: "Run `meridian db reset` to drop and recreate the schema \u2014 reset and delete stay available while you're over the limit.",
   FEATURE_NOT_ENTITLED: "Your organization's plan does not include managed development databases; upgrade it in the Meridian dashboard."
 };