@elasticias/ui 1.0.5 → 1.0.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elasticias/ui",
-  "version": "1.0.5",
+  "version": "1.0.6",
   "peerDependencies": {
     "@angular/common": "^21.0.0",
     "@angular/core": "^21.0.0",

package/types/elasticias-ui.d.ts

@@ -966,8 +966,16 @@ declare class EfBuildStampComponent {
     readonly owner: _angular_core.InputSignal<string>;
     protected readonly info: _elasticias_core.EfBuildInfo;
     protected readonly year: number;
-    /** Commit and branch always identify a build; a version only appears when
-     *  the app actually maintains one, so an unversioned app shows no `v`. */
+    /**
+     * A released build is known by its version; an unreleased one has no
+     * version to be known by, so it shows what actually identifies it.
+     *
+     * That is not a cosmetic split. Only production is cut from a tag, so
+     * only production has a number a person can repeat back to you. On
+     * develop and staging the honest answer is where it came from and when.
+     */
+    protected readonly label: _angular_core.Signal<string>;
+    /** The rest of the identity, for when the label is only a version. */
     protected readonly detail: _angular_core.Signal<string>;
     static ɵfac: _angular_core.ɵɵFactoryDeclaration<EfBuildStampComponent, never>;
     static ɵcmp: _angular_core.ɵɵComponentDeclaration<EfBuildStampComponent, "ef-build-stamp", never, { "owner": { "alias": "owner"; "required": false; "isSignal": true; }; }, {}, never, never, true, never>;