* fix(deploy): let webhooks and CLI accept reviewed Compose changes
Webhook and CLI deploys hit COMPOSE_REVIEW_REQUIRED with no way through the gate, and the refusal hid what changed. Accept the current Compose source explicitly per deploy (--accept-compose-changes, or acceptComposeChanges on the hook), and surface the added/changed/removed services in the CLI error and the webhook delivery record.
* test(contracts): include acceptComposeChanges in deployment schema flags
The Compose review gate added acceptComposeChanges to
CreateDeploymentSchema without updating the contract test that
enumerates the schema's public flags, so the contracts suite failed
on CI. Add the flag to the expected list.
* docs(cli): list --accept-compose-changes in the deploy reference
The new deploy flag was missing from the generated CLI reference,
so docs:check failed with a stale reference. Add the row in
declaration order.
* Retain explicit Compose approval through shared deployment admission
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
* feat(dns): add DigitalOcean DNS provider support
- Add DigitalOcean DNS management for custom domains and DNS-verified HTTPS
- Preserve record ownership with paired TXT markers and update provider setup guidance
* fix(dns): parse DigitalOcean record IDs from formatted JSON
- Handle compact and pretty-printed API responses, with a fallback when Python is unavailable
- Cover record cleanup and API error responses in DNS hook tests
* fix(dns): harden DigitalOcean DNS provider after review
- Decode TXT input before writing so quoted values compare in-sync
- Treat zones not delegated to DigitalOcean nameservers as pending
- Resolve zones with one paginated domain list and strip wildcard labels
- Carry credential id and provider on unauthorized lookups so the
reconnect modal targets the rejected credential
- Clean up ownership markers when the marked record is already gone
- Report read-only token verification accurately and surface missing
write scope on 403
- Guard token redaction and requests against an empty token
- Share DNS name helpers and the DNS-01 cleanup hook template
* fix(dns): release owned records from inactive DigitalOcean zones
- Allow DNS cleanup to resolve inactive zones while keeping writes restricted to active zones
- Fetch DigitalOcean records and ownership markers concurrently
* fix(dns): resolve provider credentials oldest first
* Require strict JSON record IDs before DNS challenge cleanup
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
* Protect support intake and add mailbox sender blocking
* Regenerate support operator route reference
* Wire contact widget key into the website runtime
* Fix repeat contact challenges and classify private support blocks
* feat: add platform migrations and refresh the Cloud experience
* fix(ci): run MongoDB 8 imports on compatible runners
* docs(web): add Railway and Vercel migration pages
* feat(dashboard): add shared dotenv text editing and top add action
* fix(dashboard): wrap text editor actions on narrow screens
* feat(billing): unify plan management and referral navigation
* docs(billing): describe plan management and align summary assertions
* test(billing): align named plan and accessible summary assertions
* fix(build): scale the managed build-cache budget with the disk
The managed project-cache budget was min(5 GiB, 10% of the Docker
filesystem). A project whose BuildKit cache outgrew 5 GiB was evicted by
the post-build prune after every build, so every deploy started cold.
- buildCacheKeepBytes is now 20% of the Docker filesystem, so the budget
follows the disk in both directions: disks under 50 GiB also move from
10% to 20%. This also applies to managed Cloud workers, which share
the collector.
- Below the 20% free-space GC target the idle budget shrinks to what
still fits above it (never below the old min(5 GiB, 10%)), so idle
caches give space back before rollback artifacts and running apps.
BuildKit's own 20% minFreeSpace still bounds a running worker.
- pruneManagedBuildCaches defaults to that budget instead of 5 GiB.
- The daily sweep marks its call as automaticRetention, so managed caches
use the same budget; keepStorageBytes still bounds native Docker cache.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(servers): configurable build-cache budget per server
Adds an optional managed build-cache budget for remote deployment
servers, edited from a Build cache card on the server Overview tab and
through the existing server update API, CLI and MCP tool. Empty keeps the
automatic share of the Docker filesystem.
- servers.build_cache_budget_bytes (migration 0224), bounded 1 GiB to
64 TiB in the database and the API contract.
- Only remote deployment servers expose and accept it: the local row
builds through the host daemon's native cache and migration sources
never build, so updates there are refused; managed Cloud servers keep
rejecting every field except name. Changing it requires server admin,
since a large budget lets caches hold most of the disk.
- SSH Docker runtimes read the value through a new buildCacheBudgetBytes
connection option on every collection, so a change applies to the next
build without reconnecting. It sets the post-build prune budget,
BuildKit's maxUsedSpace and the daily sweep's managed budget, capped at
the filesystem minus the admission reserve and still reduced under
storage pressure; a failed read falls back to automatic.
- Updates are audited like gpuOverride and do not drop retained SSH
sessions.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: regenerate the MCP and CLI references for the build-cache budget
The server update tool description and the `server configure` help now
mention the build-cache budget, so the generated references changed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(migration): frame streamed rsync progress updates
* fix(migration): preserve exact progress with rsync byte units
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
* feat(mail): expose fail2ban status, ban and unban via API and MCP
* feat(mail): manage Fail2ban bans from the existing Health tab
* fix(mail): preserve exact IP display in RTL ban reviews
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
* feat(auth): add generic oidc login for self-hosted dashboards
Register a Better Auth generic-oauth provider (id oidc) when OIDC_ISSUER, OIDC_CLIENT_ID and OIDC_CLIENT_SECRET are all set, advertise it with its OIDC_DISPLAY_NAME label, and render it on login and registration. Existing users link only when the IdP sends email_verified true, the invite-only gate still applies, and zero-auth instances reject the OAuth2 routes. Refs #1469.
* fix(auth): verify oidc id tokens against the issuer jwks
Verify the ID token signature against the discovered JWKS with the configured issuer, client audience, time claims and authorized party, and fail closed instead of falling back to userinfo. Require discovery issuer equality, require https for production endpoints except loopback, and route the code exchange through the validated token endpoint. Addresses review on #1489.
* fix(auth): validate the oidc authorize endpoint and expire discovery
Refuse OIDC sign-in unless discovery validates, require and pin the authorization endpoint the redirect uses, expire cached discovery after one hour and fail closed on a failed refresh, and cover the production issuer boot check. Addresses review on #1489.
* refactor(auth): inject the oidc discovery loader into account security
Pass loadOidcDiscovery through the plugin options like getAuthMode instead of a lazy import, so the module keeps no runtime dependency on the env-loading provider code.
* fix: verify OIDC identities and bind tokens to sign-in state
* fix(auth): isolate OIDC identities and enforce self-hosted login boundaries
* test(auth): align SDK parity config mock with OIDC policy
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
* feat: add runtime security advisories and annual Cloud billing
* fix(updates): show runtime advisories in the global update center
* fix(updates): synchronize advisory consent across global views
* refactor(updates): reuse normal refresh and environment flow
* fix(security): pin patched Node and Bun runtimes across releases
* fix(build): pass bootstrap selection independently of eval arguments
* test(build): expect the patched default Bun image in detection
* docs: prepare 0.9.4 changelog since 0.9.3
* fix: queue pushes during a running deploy
A push that lands while its project is still deploying is now recorded as queued and deployed when that deployment finishes, instead of failing for good.
* fix(deploy): share durable admission for queued pushes
* fix(deploy): revalidate approvals before automatic cancellation
* test(deploy): align admission mocks and migration expectations
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
Merge the updated Swarm discovery parent and regenerate MCP references. Match the wizard to the existing self-hosted controller gate so hosted BYOC cannot stage unsupported route passwords. Cover hosted BYOC, self-hosted servers, cloud targets, and cluster targets with the real editor.