v0.10.0

chore(release): v0.10.0

v0.9.0

FEATURES:

• Added runner/job-worker integration coverage: daytona_job_poll, daytona_update_job_status, daytona_authenticated_runner, and daytona_runner_healthcheck.
• Added daytona_update_sandbox_state for runner/control-plane integrations that need to report sandbox state directly.
• Added raw build-log data sources for sandbox and snapshot builds. Daytona marks these endpoints deprecated; the existing build-log URL data sources remain preferred for new Terraform configurations.

NOTES:

• Bumped the Daytona Go API client to v0.189.0.
• Added an OpenAPI endpoint coverage test so non-deprecated generated SDK methods fail tests when they are not covered by the provider or explicitly classified.
• Updated GitHub install and module examples to v0.9.0.

v0.8.1

0.8.1 (2026-06-23)

NOTES:

• Refactored provider internals for configure handling, collection data source readers, sandbox update orchestration, create-state persistence, GPU projection, and sandbox HTTP test helpers. No provider schemas changed.
• Updated GitHub install and module examples to v0.8.1.

v0.8.0

chore(release): v0.8.0

v0.7.0

chore(release): v0.7.0 — migrate to 536tech namespace (#17)

Move provider publishing to 536tech/daytona with the new 536Tech
release-signing key. Add the azure-runner-fleet use-case example and a
cli-vs-terraform doc. No provider functionality changed.

v0.6.0

0.6.0 (2026-06-16)

FEATURES:

• daytona_sandbox: added persistent volume mounts with optional subpaths.
• daytona_sandbox: added ordered GPU type preferences, assigned gpu_type, Dockerfile build_info, and last_activity_at state.
• daytona_snapshot: added ordered GPU type preferences, assigned gpu_type, and Dockerfile build_info state.

NOTES:

• Added unit and acceptance coverage for the new sandbox and snapshot fields. The sandbox GPU acceptance test is gated by DAYTONA_ACC_GPU because it requires live GPU quota.

v0.5.0

v0.5.0

v0.4.3

v0.4.3

v0.4.2

fix: do not retry non-idempotent mutations

The v0.4.0 retry wrapper used retryablehttp's default policy, which
retries 5xx and connection errors for every method. A create whose
response was lost could be replayed and duplicate a billable Daytona
resource.

Gate retries with safeRetryPolicy: retry 429 for any request (the server
rejects it before processing), retry 5xx only for idempotent methods
(GET/HEAD/PUT/DELETE), and never retry transport errors. Add a
table-driven policy test plus client tests proving a PATCH 500 is not
retried while a PATCH 429 is. Prepare the v0.4.1 release.

v0.4.1

v0.4.1