v0.1.7

Claim-time AI credential provisioning, claim-script env var injection, and removal of forced claim redeploy wait.

v0.1.6

What's changed

• Reuse existing amazeeclaw key tokens when a matching key exists for the same team and region
• Create a new key only when no matching regional shared key is found
• Use deterministic key naming: amazeeclaw-team-{teamId}-region-{regionId}

Why

This enforces shared key usage across instances in the same region/team and improves budget control while still allowing separate keys per region.

v0.1.5

What's changed

• Replace project-name suffix generation based on substr(uniqid(), 0, 4) with secure random hex (random_bytes)
• Keep a hashed fallback path if secure randomness is unavailable

Why

This prevents repeated suffixes across instance creations and makes generated project names much more distinct.

v0.1.4

What's changed

• Resolve OpenClaw default model from Store App app_config.openclaw_default_model when instance-level value is not set
• Continue to prioritize instance-level model overrides when provided
• Inject resolved value into Lagoon as AMAZEEAI_DEFAULT_MODEL

Why

Ensures Store App default model is consistently applied to new instances even when instance-specific configuration is left blank.

v0.1.3

What's changed

• Add store-level app-specific configuration field for openclaw_default_model so it appears in Polydoc app setup
• Keep instance-level override field for openclaw_default_model
• Apply store-level app_config_openclaw_default_model as fallback when instance-level value is not set

Why

This ensures the app class surfaces app-specific fields in Polydoc while still supporting per-instance overrides.

v0.1.1

Adds team-based amazee.ai provisioning, request email enforcement, and customizable OpenClaw pre-create naming strategy.

v0.1.0

Changes

• move polydock-app-amazeeio-generic and polydock-amazeeai-backend-client-php constraints to ^0.1
• keeps dual-key provisioning logic introduced in previous release line

v0.0.3

Changes

• provision both LiteLLM and backend API credentials during post-create
• create backend API token scoped to the provisioned backend user
• inject new instance env var AMAZEEAI_BACKEND_API_TOKEN
• bump backend client dependency to ^0.0.8

v0.0.2

Changes

• bump freedomtech-hosting/polydock-app-amazeeio-generic to ^0.0.81

This keeps AmazeeClaw compatible with the backend client v0.0.7 dependency line.

v0.0.1

Changes

• initial published release of amazeeio/polydock-app-amazeeclaw
• refactor app to inherit from generic Polydock AI app and keep only AmazeeClaw-specific overrides
• add package README and OpenClaw default model field guidance