Repository navigation
feat(projects): configure container build autoscaling - #634
Merged
Merged
Conversation
There was a problem hiding this comment.
Risk: medium. Cursor Bugbot completed successfully with no findings requiring human review, so this change is approved. The CLI autoscaling flags are additive with validation and tests, and they stay within the configured risk threshold.
Sent by Cursor Approval Agent: Pull Request Router and Approver
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Project commands can now configure the public API's container build autoscaling threshold and display its current value.
max_concurrent_buildsas a number ornull. Get/update text includes “Builds per instance”.Validation: full Go test suite, golangci-lint, formatting and dependency checks; GoReleaser snapshot builds for all 10 targets; npm formatting, type-check, and package build.
Note
Medium Risk
Touches project autoscaling configuration sent to the API, which affects builder scaling behavior, though changes are additive with validation and broad test coverage.
Overview
Adds CLI support for container build autoscaling on Depot projects: concurrent builds per builder instance before horizontal scaling kicks in.
depot projects createaccepts optional--max-concurrent-builds(positive int; omitted leaves autoscaling off for new projects).depot projects updateadds--max-concurrent-buildsand--disable-autoscaling(mutually exclusive); omitting both leaves the current setting. Invalid values and conflicting flags are rejected before auth or API calls. Disable sends an explicitnullviaNullableInt32.Get/create/update output now surfaces the setting: JSON field
max_concurrent_builds(number ornull), text line Builds per instance (or Disabled). README and command help/examples are updated accordingly.New
autoscaling_test.goexercises create/update requests, null serialization, output formats, and pre-auth validation; existing project tests are extended for the new update requirements and mock responses.Reviewed by Cursor Bugbot for commit 2d719e7. Bugbot is set up for automated code reviews on this repo. Configure here.