Changes to Update auto-apply for deploy request

PUT /organizations/{organization}/databases/{database}/deploy-requests/{number}/auto-apply

Every recorded change to this endpoint, newest first. Back to the operation

Changed in 4 of the 24 revisions of this API.394

Jul 8, 2026fa19f33052411
Jun 1, 202672506953f367373
Dec 9, 2025d710019068fb1
Dec 6, 2025477c6ebdabdf1

What changed

Jul 8, 2026fa19f33052411See the full diff
- ○
  added the required property into_branch_keyspace_count to the response with the 200 status
  response-required-property-added
Jun 1, 202672506953f367373See the full diff
- ▲
  the response property branch_deleted_at became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property branch_deleted_by became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property closed_at became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property closed_by became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployed_at became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/actor became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/cancelled_actor became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/cutover_actor became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/cutover_at became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/deploy_check_errors became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/deploy_operation_summaries/items/table_recently_used_at became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/deploy_operation_summaries/items/throttled_at became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/deploy_operations/items/deploy_error_docs_url became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/deploy_operations/items/deploy_errors became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/deploy_operations/items/eta_seconds became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/deploy_operations/items/progress_percentage became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/deploy_operations/items/removed_foreign_key_names became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/deploy_operations/items/table_recently_used_at became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/deploy_operations/items/throttled_at became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/deployment_revert_request became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/finished_at became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/locked_table_name became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/queued_at became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/ready_to_cutover_at became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/schema_last_updated_at became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/started_at became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/submitted_at became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property deployment/throttler_configurations became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property branch_deleted_by became optional for the status 200
  response-property-became-optional
- ▲
  the response property closed_by became optional for the status 200
  response-property-became-optional
- ▲
  the response property deployment/actor became optional for the status 200
  response-property-became-optional
- ▲
  the response property deployment/cancelled_actor became optional for the status 200
  response-property-became-optional
- ▲
  the response property deployment/cutover_actor became optional for the status 200
  response-property-became-optional
- ▲
  the response property deployment/deploy_check_errors became optional for the status 200
  response-property-became-optional
- ▲
  the response property deployment/locked_table_name became optional for the status 200
  response-property-became-optional
- ▲
  the response property deployment/throttler_configurations became optional for the status 200
  response-property-became-optional
- ▲
  the deployment/throttler_configurations response's property type/format changed from array/ to object/ for status 200
  response-property-type-changed
- ○
  added the required property deployment/force_cutover_requested_at to the response with the 200 status
  response-required-property-added
- ○
  added the required property deployment/queue_pause_reason to the response with the 200 status
  response-required-property-added
- ○
  added the required property deployment/queue_paused to the response with the 200 status
  response-required-property-added
Dec 9, 2025d710019068fb1See the full diff
- ▲
  for the path request parameter number, the type/format was changed from number/ to integer/
  request-parameter-type-changed
Dec 6, 2025477c6ebdabdf1See the full diff
- ▲
  for the path request parameter number, the type/format was changed from string/ to number/
  request-parameter-type-changed