|
|
|
January Release Notes
|
|
Here's what shipped in January!
|
|
git/clone 2.0.0
|
|
git/clone 2.0.0 has been released with built-in support for incremental fetching via tool caches. To upgrade, run rwx update --allow-major-version-change, rename github-access-token to github-token, and configure a tool cache on your run definition.
|
|
Flow View
|
|
We've just released a Flow view of runs, located right in between the Tasks and Timeline tabs. See each task's dependencies in relation to each other, with a birds-eye view of the entire run.
|
|
Webhook Triggers
|
RWX now supports triggering runs via webhooks from third-party services. Check out the docs to get started.
|
|
RWX CLI v3.0.0
|
|
RWX CLI v3.0.0 is released. rwx run now supports a --wait flag to wait for a run to complete or reach its first failure and print additional troubleshooting information. rwx results shows the same information for existing runs.
|
|
|
|
Copy Prompt Button
|
|
Runs with failed tasks now have a "Copy Prompt" button in the UI, to easily grab the relevant details for your AI agents.
|
|
IPv6 Networking
|
|
IPv6 networking is now supported within tasks. You can interact with dual-stack and IPv6-only services on RWX.
|
|
CLI Artifact Download
|
|
With version 2.3.5 of the RWX CLI, you can now download artifacts for a task using rwx artifacts download <task-id> <artifact-key>.
|
|
MCP Server Errors
|
|
The RWX MCP Server can now return information on initialization errors, to help AI assistants debug configuration errors in run definitions.
|
|
CLI Logs
|
With version 2.3.0 of the RWX CLI, you can now pull logs for any given task using rwx logs <taskId>. See the blog post.
|
|
Release Notes in UI
|
|
We're now exposing release notes in the UI and in the docs. We'll light up the rocket when we've shipped something new, so you can stay up to date on everything going on with RWX.
|
|
Change the Workspace Directory
|
You can now change the workspace directory, which is especially helpful when building container images natively on RWX. See the docs.
|
|
Ingest Telemetry into Sentry
|
|
|
|
What is the state of the art in CI/CD?
|
|
|