chore: bump allocator/client to 0.4.0 and CLI to 0.3.0

README.md

@@ -90,7 +90,7 @@ Production images are built from the PyPI packages:
 - `linux-amd64-latest` - Latest for specific platform
 - `<sha>` - Specific git commit
 - `linux-amd64-test` - Development/testing builds
-- `<version>` (e.g., `0.3.0`) - Only published when a build is triggered manually
+- `<version>` (e.g., `0.4.0`) - Only published when a build is triggered manually
 
 See [Docker Image Tags](https://talmolab.github.io/lablink/workflows/#image-tagging-strategy) for complete tagging strategy.
 

packages/allocator/pyproject.toml

@@ -36,7 +36,7 @@ description = "VM Allocator Service Package for Lablink"
 name = "lablink-allocator-service"
 readme = "README.md"
 requires-python = ">=3.10"
-version = "0.3.0"
+version = "0.4.0"
 
 [project.optional-dependencies]
 config = []  # Config schema only (pure dataclasses, no heavy deps)

packages/cli/CHANGELOG.md

@@ -5,12 +5,27 @@ All notable changes to **lablink-cli** will be documented here.
 The format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) and
 this project uses [Semantic Versioning](https://semver.org/).
 
-## [Unreleased]
+## [0.3.0] - 2026-09-08
+
+### Added
+
+- `lablink deploy` prompts (hidden input) for a Tailscale authkey or
+  Cloudflare Tunnel token when the corresponding flag is omitted, instead of
+  refusing and forcing the credential onto the command line where it lands in
+  shell history (#485).
+- `lablink doctor` warns when an `ssl.provider: none` (HTTP) deployment
+  silently disables H.264 — browsers expose WebCodecs only on secure origins,
+  so every session falls back to JPEG/WebP stills and feels laggy (#491).
 
 ### Changed
 
 - Pinned `lablink-template` bumped to
-  [v0.3.1](https://github.com/talmolab/lablink-template/releases/tag/v0.3.1).
+  [v0.3.1](https://github.com/talmolab/lablink-template/releases/tag/v0.3.1)
+  (#498).
+- `lablink-allocator-service[config]` pin raised to `>=0.4.0`: the CLI
+  re-exports `MachineConfig`, whose `ami_id` default became empty (= resolve
+  the per-region Deep Learning Base AMI) in allocator 0.4.0. An older
+  allocator would reintroduce the stale hardcoded us-west-2 AMI default.
   `app.region` now actually drives the deployment (every `.tf` file previously
   ignored it, so infrastructure landed in `us-west-2` regardless), and the
   allocator boots stock Ubuntu 24.04 resolved per region from an SSM parameter
@@ -20,6 +35,33 @@ this project uses [Semantic Versioning](https://semver.org/).
   deployment first: existing `us-west-2` resources are not moved and keep
   billing.
 
+### Fixed
+
+- `lablink doctor`'s AMI check verifies the image actually exists in the
+  target region instead of trusting `AMI_MAP`, which listed four regions all
+  mapped to one us-west-2-only image — a false green that ended in
+  `InvalidAMIID.NotFound` at deploy time (#484).
+- An empty `machine.ami_id` is treated as "resolve the per-region Deep
+  Learning Base AMI fallback" (matching what the deployment does since #489)
+  instead of failing `doctor` with `No machine.ami_id set` (#490).
+
+## [0.2.0] - 2026-08-31
+
+### Added
+
+- External-runtime deploy mode: `lablink deploy --render-only` writes the
+  compose bundle without running Docker, for platforms where the CLI host
+  can't run the allocator itself (#472).
+
+### Changed
+
+- BYO clients ship their own container logs from inside the client container;
+  the CLI's detached log-shipper process is dropped. Requires
+  `lablink-client-service` >= 0.3.0 images (#479).
+- Every manual-deployment fact is routed through one `manual.py` module (#467).
+- The wizard and `lablink deploy` warn about Let's Encrypt's 5-certs/7-days
+  rate limit before reusing a domain (#474).
+
 ## [0.1.0] - 2026-08-17
 
 First stable release (supersedes the `0.1.0a1` prerelease).

packages/cli/pyproject.toml

@@ -5,15 +5,15 @@ authors = [
   {name = "Talmo Pereira", email = "talmo@salk.edu"},
   {name = "Andrew Park", email = "hep003@ucsd.edu"},
 ]
-version = "0.2.0"
+version = "0.3.0"
 description = "CLI tool for deploying and managing LabLink infrastructure"
 readme = "README.md"
 requires-python = ">=3.10"
 dependencies = [
     # >=0.2.0: deploy_compose imports PUBLIC_HOSTNAME_HINT,
     # is_valid_public_hostname and is_weak_admin_password, none of which
     # exist in 0.1.2 — an unpinned resolve breaks `provider: manual`.
-    "lablink-allocator-service[config]>=0.2.0",
+    "lablink-allocator-service[config]>=0.4.0",
     "typer>=0.15",
     "textual>=3.0",
     "rich>=13.0",

packages/client/pyproject.toml

@@ -28,7 +28,7 @@ keywords = ["vm", "docker", "postgres", "tutorial", "AWS"]
 name = "lablink-client-service"
 readme = "README.md"
 requires-python = ">=3.10"
-version = "0.3.0"
+version = "0.4.0"
 
 [project.optional-dependencies]
 dev = ["twine", "build", "pytest", "ruff", "pytest-cov"]