@the-meridian/cli 1.0.0 → 1.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +6 -0
- package/dist/index.js +1 -1
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,11 @@
|
|
|
1
1
|
# @the-meridian/cli
|
|
2
2
|
|
|
3
|
+
## 1.0.1
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 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.
|
|
8
|
+
|
|
3
9
|
## 1.0.0
|
|
4
10
|
|
|
5
11
|
### Major Changes
|
package/dist/index.js
CHANGED
|
@@ -452,7 +452,7 @@ function extractErrorCode(body) {
|
|
|
452
452
|
return record !== void 0 && typeof record.error === "string" ? record.error : void 0;
|
|
453
453
|
}
|
|
454
454
|
var HINTS_BY_ERROR_CODE = {
|
|
455
|
-
dev_database_limit_reached: "
|
|
455
|
+
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.",
|
|
456
456
|
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.",
|
|
457
457
|
FEATURE_NOT_ENTITLED: "Your organization's plan does not include managed development databases; upgrade it in the Meridian dashboard."
|
|
458
458
|
};
|