@zerotal/admin 1.5.1 → 1.6.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 +11 -0
- package/package.json +9 -9
- package/src/ui/environmentIndicator.tsx +7 -1
package/CHANGELOG.md
CHANGED
|
@@ -8,6 +8,17 @@ follows the Zerotal monorepo's unified versioning.
|
|
|
8
8
|
|
|
9
9
|
## [Unreleased]
|
|
10
10
|
|
|
11
|
+
## [1.6.0] — 2026-08-15
|
|
12
|
+
|
|
13
|
+
### Fixed
|
|
14
|
+
|
|
15
|
+
- **The environment badge showed on every screen, and always said the same thing.** It read
|
|
16
|
+
`APP_ENV`, which holds the runtime mode once the app has booted — so it rendered `web`,
|
|
17
|
+
which is in nobody's quiet list, and its `staging` tone could never fire. A badge whose
|
|
18
|
+
whole purpose is preventing "I thought this was staging" was displaying the same wrong word
|
|
19
|
+
in every environment. It reads `deployEnv()` now, so local stays quiet and staging is
|
|
20
|
+
visibly staging.
|
|
21
|
+
|
|
11
22
|
## [1.5.1] — 2026-08-15
|
|
12
23
|
|
|
13
24
|
### Fixed
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@zerotal/admin",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.6.1",
|
|
4
4
|
"license": "MIT",
|
|
5
5
|
"maturity": "stable",
|
|
6
6
|
"private": false,
|
|
@@ -31,16 +31,16 @@
|
|
|
31
31
|
"typecheck": "tsc --noEmit"
|
|
32
32
|
},
|
|
33
33
|
"dependencies": {
|
|
34
|
-
"@zerotal/cache": "1.
|
|
35
|
-
"@zerotal/core": "1.
|
|
36
|
-
"@zerotal/flow": "1.
|
|
37
|
-
"@zerotal/flow-ui": "1.
|
|
38
|
-
"@zerotal/validator": "1.
|
|
34
|
+
"@zerotal/cache": "1.6.1",
|
|
35
|
+
"@zerotal/core": "1.6.1",
|
|
36
|
+
"@zerotal/flow": "1.6.1",
|
|
37
|
+
"@zerotal/flow-ui": "1.6.1",
|
|
38
|
+
"@zerotal/validator": "1.6.1"
|
|
39
39
|
},
|
|
40
40
|
"devDependencies": {
|
|
41
|
-
"@zerotal/orm": "1.
|
|
42
|
-
"@zerotal/auth": "1.
|
|
43
|
-
"@zerotal/queue": "1.
|
|
41
|
+
"@zerotal/orm": "1.6.1",
|
|
42
|
+
"@zerotal/auth": "1.6.1",
|
|
43
|
+
"@zerotal/queue": "1.6.1"
|
|
44
44
|
},
|
|
45
45
|
"peerDependencies": {
|
|
46
46
|
"@zerotal/orm": "^1.0.0",
|
|
@@ -6,6 +6,7 @@
|
|
|
6
6
|
// admin panel ecosystem grows a plugin for exactly this.
|
|
7
7
|
|
|
8
8
|
import type { HtmlNode } from "@zerotal/flow";
|
|
9
|
+
import { deployEnv } from "@zerotal/core";
|
|
9
10
|
import type { RenderHook } from "../renderHooks.ts";
|
|
10
11
|
|
|
11
12
|
export interface EnvironmentIndicatorOptions {
|
|
@@ -41,7 +42,12 @@ export function environmentIndicator(options: EnvironmentIndicatorOptions = {}):
|
|
|
41
42
|
const tones = { ...DEFAULT_TONES, ...(options.tones ?? {}) };
|
|
42
43
|
|
|
43
44
|
return (): HtmlNode | null => {
|
|
44
|
-
|
|
45
|
+
// `deployEnv()` — `APP_ENV` holds the runtime mode by the time a page renders, so
|
|
46
|
+
// this badge read "web": never in the quiet list, so it showed on every screen
|
|
47
|
+
// including local, and its `staging` tone could never fire. The one mistake this
|
|
48
|
+
// component exists to prevent is editing production believing it is staging, and
|
|
49
|
+
// a badge that always says the same wrong word prevents nothing.
|
|
50
|
+
const env = (options.environment ?? deployEnv()).trim();
|
|
45
51
|
if (!env || quiet.has(env.toLowerCase())) return null;
|
|
46
52
|
|
|
47
53
|
const tone = tones[env.toLowerCase()] ?? "bg-amber-500 text-black";
|