For AI agents: markdown of this page — /docs-content-en/changelog/infra-deploy.md documentation index — /llms.txt
Change history: Deploy API
← Changelog. Entries: 116.
- 2026-09-30 NEW-0930-34: server activity feed
- 2026-09-28 FIX-0928-16: warning about application access to the Bitrix24 account after deploy
- 2026-09-25 FIX-0925-5: the sleeping-app log read no longer names a wake address that is banned on the host
- 2026-09-25 BC-0925-21: deploying with a Read-only key does not post the new version announcement
- 2026-09-23 NEW-0923-12: server detail returns the last deploy's start command, install command and port
- 2026-09-22 FIX-0922-13: a wake schedule can be set for an app inside a galaxy again
- 2026-09-21 FIX-0921-3:
/execno longer corrupts multi-byte characters in output - 2026-09-19 FIX-0919-2: a lost link to the cloud machine is no longer reported as its absence, and no longer advises creating a second one
- 2026-09-18 BC-0918-2: A server development-team member gets their own key, and the key block gains the collaborator slot
- 2026-09-17 BC-0917-11: a galaxy command with no exit status is no longer reported as successful
- 2026-09-17 BC-0917-12: an empty query-parameter value in the operations list is no longer replaced by the default
- 2026-09-17 NEW-0917-13: the outcome of a server command is readable after an interrupted wait
- 2026-09-17 FIX-0917-14: on a busy server the machine-actionable recovery field names the guarded endpoint
- 2026-09-16 FIX-0916-7: API reports the effective tunnel state
- 2026-09-15 FIX-0915-10: external collaborator keys are bound to their server
- 2026-09-15 BC-0915-15: a read-only key can deploy an application to its own server again
- 2026-09-14 FIX-0914-18: the dedicated server card returns the installed runtime after a successful deploy
- 2026-09-09 FIX-0909-8: the spec declares the 429 refusal of endpoints that carry their own rate limit
- 2026-09-01 FIX-0901-7: a transient image-registry outage no longer marks a galaxy app broken
- 2026-08-28 BC-0828-5: Deploy outcomes can be confirmed after a dropped connection
- 2026-08-28 FIX-0828-11: commands in a galaxy app are no longer refused before dispatch
- 2026-08-28 FIX-0828-13: A ZIP deploy no longer asks you to change the archive format when the server is busy with another command
- 2026-08-27 BC-0827-2: runtime installation order and nginx startup have changed
- 2026-08-26 BC-0826-2: exec into a Galaxy app answers CONTAINER_NOT_READY instead of a false success
- 2026-08-25 BC-0825-2: a read-only key no longer writes on platform endpoints
- 2026-08-25 BC-0825-7: deploy base version is required when the top saved source version belongs to somebody else too
- 2026-08-25 BC-0825-10: Inline archive cap on the deploy body narrowed to 96 MB
- 2026-08-25 FIX-0825-13: Node.js 20 runtime setup no longer repeats completed steps
- 2026-08-23 NEW-0823-2: several employees can work on one application's code
- 2026-08-22 FIX-0822-7: Reliable source downloads for dedicated VM deploys
- 2026-08-21 BC-0821-8: a busy shared galaxy exec channel now answers 409 instead of 502
- 2026-08-17 FIX-0817-1: repeated PostgreSQL runtime deploy no longer fails on an existing database
- 2026-08-16 FIX-0816-4: the Cowork deploy-key handout no longer loses servers
- 2026-08-15 BC-0815-1: combo runtimes with a database no longer slip into Galaxy silently
- 2026-08-14 BC-0814-2: port pinning refuses instead of confirming falsely
- 2026-08-14 FIX-0814-5: the blocking server wake returns WAKE_TIMEOUT far less often on a cold start
- 2026-08-14 NEW-0814-14: a write with a lossy-charset value now reports it
- 2026-08-13 NEW-0813-3: the real state of a sleeping galaxy app in the server GET and in the logs answer
- 2026-08-12 NEW-0812-3: The app port is pinned to the server and survives a wake
- 2026-08-12 FIX-0812-11: a dedicated-machine deploy keeps the build's internal links and checks the application root
- 2026-08-12 FIX-0812-14: a key allowed to deploy can also patch the application on that server
- 2026-08-12 NEW-0812-16: deploy operation id and after-the-fact outcome reconciliation
- 2026-08-11 NEW-0811-2: the application data directory is declared in the deploy body
- 2026-08-11 BC-0811-14: deploy no longer reports success when the port stayed with the previous process
- 2026-08-11 NEW-0811-24: an interrupted galaxy deploy now names its cause and flags repeats
- 2026-08-11 BC-0811-26: uploading a file to a galaxy app is refused instead of writing to the shared server
- 2026-08-10 FIX-0810-6: a host out of free disk space is a distinct retryable deploy failure, not a broken app
- 2026-08-10 BC-0810-14: commands, deploys and file uploads addressed by a galaxy host id are refused
- 2026-08-10 FIX-0810-19: preserveEnv no longer loses .env when a deploy fails after the directory is cleaned
- 2026-08-07 FIX-0807-2: a source version deploys by its number on its own server
- 2026-08-07 BC-0807-6: an AI agent's server no longer accepts an application deploy
- 2026-08-07 FIX-0807-8: the galaxy host now fetches the source archive itself
- 2026-08-07 FIX-0807-9: a deploy no longer fails while stopping a slow application
- 2026-08-07 NEW-0807-15: deploy now reports a displayName or description it did not apply
- 2026-08-06 FIX-0806-8: galaxy app exec now targets the container by its real name
- 2026-08-06 NEW-0806-10: deploying a galaxy app from a link or a saved version
- 2026-08-06 FIX-0806-17: base image registry unavailable during a galaxy app build is now transient, not fatal
- 2026-08-06 FIX-0806-19: the platform now passes the application its port in the PORT variable
- 2026-08-05 NEW-0805-6: deploy warns when the verified app path disagrees with the address Bitrix24 opens
- 2026-08-05 FIX-0805-8: the tunnel survives an app restart, and port auto-detection no longer loses the target
- 2026-08-05 NEW-0805-20: creating a server with inline code joined the shared queue for heavy requests
- 2026-08-04 NEW-0804-10: Gateway timeout on exec now carries a recovery hint
- 2026-08-04 FIX-0804-12: a multipart archive deploy now keeps the source version even when the deploy fails
- 2026-08-03 FIX-0803-3: server creation now says plainly when it returned the application's existing server
- 2026-08-03 NEW-0803-11: the one-shot galaxy app create now accepts
healthPath - 2026-08-03 FIX-0803-12:
/startand/wakeon a galaxy app now explain why they do not apply - 2026-08-03 FIX-0803-14:
/rebooton a sleeping galaxy app now kicks the host repair and says so - 2026-08-03 FIX-0803-15: a zip source archive no longer fails at extraction on a galaxy app
- 2026-08-03 NEW-0803-16: Source versions accept up to 500 MB, and a deploy from our own link now links to the version on any key
- 2026-08-01 FIX-0801-2: galaxy app deploy no longer reports an interruption after an update that actually succeeded
- 2026-08-01 BC-0801-6: a broken exec no longer answers with success and exitCode -1
- 2026-08-01 FIX-0801-7: the JSON response body of /exec and /deploy now starts with an opening brace
- 2026-07-30 FIX-0730-4: /v1/me no longer advertises access-token endpoints while the feature is off
- 2026-07-30 BC-0730-6: a galaxy is no longer created on the free Bitrix24 plan
- 2026-07-29 FIX-0729-7: galaxy app deploy verifies reachability and returns steps
- 2026-07-29 FIX-0729-9: deploy no longer reports a false success after a hardened-unit rollback
- 2026-07-29 FIX-0729-17: restart a galaxy app via /reboot
- 2026-07-28 NEW-0728-2: stuck-lock release is now cross-replica; the DELETE /lock response carries broadcast and localLock
- 2026-07-27 NEW-0727-1: app favicon in one line — /_gw/icon
- 2026-07-27 FIX-0727-3: galaxy apps: PATCH /sleep and PATCH /port now return 400 — manage them from the Galaxies page
- 2026-07-27 FIX-0727-4: galaxy app recovers after its host tunnel drops
- 2026-07-27 NEW-0727-5: warning when a deploy changelog has nowhere to be published
- 2026-07-25 NEW-0725-1: deploy: optional changelog field
- 2026-07-24 FIX-0724-5: deploy: an app wrapped in a single archive folder no longer fails with ENOENT package.json
- 2026-07-23 NEW-0723-2: sources of a deleted server: access, cleanup, and an honest answer for purged bytes
- 2026-07-23 FIX-0723-3: galaxy app deploy: a mid-build tunnel drop is no longer masked as "host unreachable"
- 2026-07-23 NEW-0723-4: deploy step timeout error now carries a recovery hint
- 2026-07-22 NEW-0722-3: deploy 409 SERVER_NOT_READY now signals it is retryable
- 2026-07-21 FIX-0721-7: Versioned deploy runtimes install the advertised version on Ubuntu 24.04
- 2026-07-18 FIX-0718-1: deploy reuses the application's server instead of creating a duplicate
- 2026-07-18 FIX-0718-2: DELETE /lock now releases a stuck lock even on a deleted server
- 2026-07-17 FIX-0717-1: deploying to a sleeping galaxy host now answers before client timeouts
- 2026-07-17 NEW-0717-4: EXEC_BUSY tells you when to retry
- 2026-07-17 FIX-0717-5: deploying a galaxy app with an oversized archive returns 413, not "host unreachable"
- 2026-07-17 NEW-0717-6: displayName and description on deploy set the Bitrix24 catalog card
- 2026-07-17 FIX-0717-7: galaxy deploy returns 503 on transient database overload
- 2026-07-16 FIX-0716-2: env sent as a file in a multipart deploy is no longer silently ignored
- 2026-07-16 FIX-0716-3: large source.content deploys no longer fail with Gateway HTTP 413
- 2026-07-14 NEW-0714-27: recover a stuck server exec channel
- 2026-07-14 FIX-0714-29: galaxy app deploy returns an honest error instead of a false success when the connection drops mid-build
- 2026-07-13 NEW-0713-7: New preserveEnv flag keeps .env across cleanDeploy
- 2026-07-13 NEW-0713-8: failed galaxy app builds now carry a
buildHint - 2026-07-11 FIX-0711-1: galaxies: GALAXY_HOST_UNREACHABLE is now actionable — structured hint and a precise provisionError
- 2026-07-10 NEW-0710-20: localized message on OPEN-mode switch denials
- 2026-07-09 FIX-0709-6: releasing a server lock accepts an empty JSON body
- 2026-07-06 FIX-0706-5: Deploy reports an honest error when the new build did not bind the port
- 2026-07-06 BC-0706-7: dedicated error code for an oversized exec command
- 2026-07-06 NEW-0706-8: hint in the exec timeout error
- 2026-07-04 FIX-0704-4: galaxy app deploy now unpacks wrapped archives correctly and reports an empty source.content clearly
- 2026-06-29 FIX-0629-6: port change and deploy auto-routing now work out of the box on new app servers
- 2026-06-24 FIX-0624-1: galaxy app logs return container output
- 2026-06-24 NEW-0624-2: GALAXY_APP_START_FAILED deploy error code
- 2026-06-24 FIX-0624-3: blocking server wake window raised to ~5 minutes
- 2026-06-24 NEW-0624-4: placement and graduateFrom parameters on server create
- 2026-06-24 FIX-0624-5: server creation with code in source.content accepts archives up to 500 MB
- 2026-06-24 FIX-0624-12: the graduation signal fires for any galaxy app memory shortage