Repository navigation
[cli] accept sizes with units on drives --max-size - #342
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
You must have Developer access to commit code to Vercel Labs on Vercel. If you contact an administrator and receive Developer access, commit again to see your changes. Learn more: https://vercel.com/docs/accounts/team-members-and-roles/access-roles#team-level-roles |
marc-vercel
reviewed
Sep 21, 2026
marc-vercel
reviewed
Sep 21, 2026
erulkey
force-pushed
the
feat/drives-size-prompt
branch
from
September 22, 2026 20:57
48bef9e to
62d229c
Compare
marc-vercel
approved these changes
Sep 23, 2026
Merged
marc-vercel
pushed a commit
that referenced
this pull request
Oct 19, 2026
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## sandbox@4.9.0 ### Minor Changes - Add `sandbox extend` to increase a running session's timeout without changing future session defaults, and clarify `sandbox config timeout` help. ([#389](#389)) - `sandbox drives get-or-create --max-size` now accepts sizes with units (`200GiB`, `2TiB`) as well as raw bytes, and rejects input it cannot parse instead of truncating it, so `2TiB` is no longer read as 2 bytes. When `--max-size` is omitted, the printed size says where it came from: `max size: 1 TiB (set with --max-size at creation, fixed afterwards)`. ([#342](#342)) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This branch was successfully deployed
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.
sandbox drives get-or-create --max-size 2TiBcurrently parses the size as2bytes and returns an unrelated minimum-size error. Accept sizes with units (200GiB,2TiB) alongside raw bytes, and reject malformed input before calling the API.Units are case-insensitive.
GBandTBuse the same binary multipliers asGiBandTiB, matching how drive sizes are documented. When--max-sizeis omitted, the output adds(set with --max-size at creation, fixed afterwards). This also applies when retrieving an existing drive, without implying that its size is the plan default.Includes the Sandbox skill examples and generated CLI reference. The size hint applies only to
get-or-create; drive forks retain their existing summary.Validation against current main:
200GiB,2TiB, raw bytes, theGBalias, malformed input, retrieving an existing drive without a size, and creating a drive with the default size. The three test drives were deleted after verification.The changeset releases this in the next minor CLI version; merging alone does not publish the package.