Repository navigation
copy an explicitly defined run_size into the generated manifest - #376
Merged
konstantinoscs merged 2 commits intoOct 5, 2026
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
bradhe
approved these changes
Oct 5, 2026
konstantinoscs
deleted the
konstantinos/eco-1203-preserve-towerfile-run_size-in-cli-package-manifests
branch
October 5, 2026 11:15
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
A Towerfile declaring run_size = "basic.large" loses that setting when the Tower CLI builds MANIFEST. Tower reads the size from the manifest when creating the app version, so retaining it only in the archived Towerfile is insufficient. The requested compute size is silently lost at the packaging boundary.
Verified on October 5, 2026: pending Tower CLI release #375, head 8d175f2, still omits the field. Its packaging test explicitly asserts that omission based on the incorrect assumption that the backend reads the Towerfile.