luma-infra 0.1.331__tar.gz → 0.1.332__tar.gz

{luma_infra-0.1.331 → luma_infra-0.1.332}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: luma-infra
-Version: 0.1.331
+Version: 0.1.332
 Summary: Declarative deployment CLI for region-aware Nomad infrastructure.
 Author: Luma Contributors
 License-Expression: MIT
@@ -107,7 +107,7 @@ A public `cn-edge` domain does not bypass the server and jump directly to a cont
 For CI runners, install the published Python package. It provides the `luma` command without running the shell installer:
 
 ```bash
-python -m pip install "luma-infra==0.1.331"
+python -m pip install "luma-infra==0.1.332"
 ```
 
 Install without cloning the repository:
@@ -125,7 +125,7 @@ Managed-runtime identity, dependency-source policy and read-only `luma doctor --
 Install a tagged release:
 
 ```bash
-export LUMA_INSTALL_REF=v0.1.331
+export LUMA_INSTALL_REF=v0.1.332
 curl -fsSL "https://raw.githubusercontent.com/LiuTianjie/luma/$LUMA_INSTALL_REF/scripts/install-luma.sh" -o /tmp/install-luma.sh && sh /tmp/install-luma.sh
 ```
 
@@ -381,7 +381,7 @@ luma deploy status.yaml
 In CI, pass the control endpoint and management token through environment variables instead of creating a login context:
 
 ```bash
-python -m pip install "luma-infra==0.1.331"
+python -m pip install "luma-infra==0.1.332"
 
 export LUMA_CONTROL_URL="https://luma.example.com"
 export LUMA_DEPLOY_TOKEN="$CI_LUMA_MANAGEMENT_TOKEN"

{luma_infra-0.1.331 → luma_infra-0.1.332}/README.md

@@ -74,7 +74,7 @@ A public `cn-edge` domain does not bypass the server and jump directly to a cont
 For CI runners, install the published Python package. It provides the `luma` command without running the shell installer:
 
 ```bash
-python -m pip install "luma-infra==0.1.331"
+python -m pip install "luma-infra==0.1.332"
 ```
 
 Install without cloning the repository:
@@ -92,7 +92,7 @@ Managed-runtime identity, dependency-source policy and read-only `luma doctor --
 Install a tagged release:
 
 ```bash
-export LUMA_INSTALL_REF=v0.1.331
+export LUMA_INSTALL_REF=v0.1.332
 curl -fsSL "https://raw.githubusercontent.com/LiuTianjie/luma/$LUMA_INSTALL_REF/scripts/install-luma.sh" -o /tmp/install-luma.sh && sh /tmp/install-luma.sh
 ```
 
@@ -348,7 +348,7 @@ luma deploy status.yaml
 In CI, pass the control endpoint and management token through environment variables instead of creating a login context:
 
 ```bash
-python -m pip install "luma-infra==0.1.331"
+python -m pip install "luma-infra==0.1.332"
 
 export LUMA_CONTROL_URL="https://luma.example.com"
 export LUMA_DEPLOY_TOKEN="$CI_LUMA_MANAGEMENT_TOKEN"

{luma_infra-0.1.331 → luma_infra-0.1.332}/luma/__init__.py

@@ -1,3 +1,3 @@
 """Luma deployment CLI."""
 
-__version__ = "0.1.331"
+__version__ = "0.1.332"

{luma_infra-0.1.331 → luma_infra-0.1.332}/luma/assets/README.md

@@ -73,7 +73,7 @@ A public `cn-edge` domain does not bypass the server and jump directly to a cont
 For CI runners, install the published Python package. It provides the `luma` command without running the shell installer:
 
 ```bash
-python -m pip install "luma-infra==0.1.331"
+python -m pip install "luma-infra==0.1.332"
 ```
 
 Install without cloning the repository:
@@ -88,7 +88,7 @@ The installer creates a private venv and writes the command shim to `~/.local/bi
 Install a tagged release:
 
 ```bash
-curl -fsSL https://raw.githubusercontent.com/LiuTianjie/luma/main/scripts/install-luma.sh | LUMA_INSTALL_REF=v0.1.331 sh
+curl -fsSL https://raw.githubusercontent.com/LiuTianjie/luma/main/scripts/install-luma.sh | LUMA_INSTALL_REF=v0.1.332 sh
 ```
 
 Develop from source:
@@ -252,7 +252,7 @@ luma deploy status.yaml
 In CI, pass the control endpoint and management token through environment variables instead of creating a login context:
 
 ```bash
-python -m pip install "luma-infra==0.1.331"
+python -m pip install "luma-infra==0.1.332"
 
 export LUMA_CONTROL_URL="https://luma.example.com"
 export LUMA_DEPLOY_TOKEN="$CI_LUMA_MANAGEMENT_TOKEN"