-
Notifications
You must be signed in to change notification settings - Fork 1
v0.3.31 release #111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
v0.3.31 release #111
Conversation
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
Introducing black formatting for python code
- Add Towerfile generation from pyproject.toml - Support working directory parameter for file operations - Generate valid TOML format (not JSON-like) - Add parameter manipulation functions for Towerfile updates
- Add MCP server implementation using rmcp abstractions - Implement core tower operations (apps, secrets, teams, etc.) - Add proper error handling for run operations - Support both local and remote tower operations via MCP protocol
- Add OutputSink trait for pluggable output handling - Improve run completion detection and matching - Restore error handling and ctrl-c support for remote runs - Update documentation for new connection methods
- Replace Rust cucumber tests with Python BDD tests using behave - Add mock API server for isolated testing - Fix async hanging issues with proper behave async support - Implement JWT-based authentication for test scenarios - Add comprehensive test coverage for MCP operations - Include CI workflow for integration tests
- Switch from fenix to rust-overlay in Nix flake - Add uv.lock files for Python dependency management - Update logging configuration to handle setup failures gracefully - Add MCP and testing dependencies to pyproject.toml
The integration tests were failing because the mock API session endpoint response was missing required fields that were added in newer API schema versions. This caused JWT authentication to fail with "UnknownDescribeSessionValue" errors, preventing local app runs from working in tests. Changes: - Add missing required fields to mock API user response (is_confirmed, is_subscribed_to_changelog) - Add comprehensive documentation and debugging guide in tests/mock-api-server/README.md - Enhance test error messages to point to specific debugging steps - Add detailed comments in mock API explaining schema dependencies - Fix workflow file to use --color flag for better CI output 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
…use it + return empty vector for sources in towerfile gen
* Initial pass at environments management * chore: List environments as a table * Integrate feedback from @copilot --------- Co-authored-by: Ben Lovell <ben.j.lovell@gmail.com>
…kages-for-example-apps TOW-916 feat: create a tower package command
…onal logic everywhere
…l write - Remove do_run_local_capture and do_run_remote_capture functions - Remove OutputSink trait and ChannelSink implementations - Remove monitor_output_capture function - Simplify monitor_output to use output functions directly - Remove sink parameter from do_follow_run_impl and handle_run_completion - Improve error propagation in do_run_remote (use err.into() instead of tower_error) - Update MCP functions to use regular run functions instead of capture variants
fmt: cargo fmt
…-and-improve-integration-test TOW 966 add CLI regression tests and improve integration test
…ponses TOW 967 fix run errors responses
…-what-it-says-it-does TOW 965 Implement MCP server streaming output for real-time progress
…tower-cli fix: improve deploy error handling and propagation
…t-writing fix:use global output::write() function instead of sinks and conditional logic everywhere
When we see a null value for a required field, the generated code will now instruct serde to give it the default value (e.g. "" for string, [] for array, etc). This may be nonsense, of course, but it's less likely to be nonsense than "null", and makes the CLI a whole lot less brittle to bugs on the backend - a single null value shouldn't kill the rest of a response!
Update generated client 2025 09
socksy
approved these changes
Sep 30, 2025
Contributor
socksy
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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.
Uh oh!
There was an error while loading. Please reload this page.