**Major**: See service logs directly in windmill: See the logs of any workers or any servers in the
Major: See service logs directly in windmill:
See the logs of any workers or any servers in the service logs of the search modal. Log count is seen in the mini-graph and error count is in red
18 Replies
you can now edit directly the yaml of flows within the flow editor
Major: windmill CLI (wmill) installable with npm and nodeJs compatible
We've made the CLI more accessible by being directly installable from npm:
npm install -g windmill-cli. It is now the recommended setup but the deno way will continue to work for the foreseable future. We updated the git sync examples as well: https://github.com/windmill-labs/windmill-sync-example/blob/main/.github/workflows/push-on-merge.yaml
There are no changes, the command is still wmill, and you will still be able to upgrade it with wmill upgrade (but require to deno uninstall wmill && npm install -g windmill-cli first)
One focus of this quarter is to improve the on-boarding experience and reduce the steep curve to learn windmill.GitHub
windmill-sync-example/.github/workflows/push-on-merge.yaml at main ...
Contribute to windmill-labs/windmill-sync-example development by creating an account on GitHub.
you can now easily change the id of steps in flows and it will modify every step inputs that depend on it automatically
We've improved the vscode extension handling of relative paths:
- On python it will detect that you're using relative paths and warn you that
wmill sync push is required
- On typescript we're introducing a beta mode that will actually bundle the relative paths as part of the preview to avoid the need of using wmill sync push as you're developing the common logic in parallel to your script logic
We fixed paste on macos on the vscode extension (you will need to update your instance to latest)
If you updated Windmill between friday evening and now, there is a bug that will make Date arguments of bun/deno scripts be passed to the script as strings instead of Date. Update to latest release 1.398.1 to fix. Apologies for this.
Hey! You can now set progress of execution of jobs from within the script. That is the feature specifically designed for long-running jobs to help You keep track of execution of your code. You can read more in docs: https://www.windmill.dev/docs/advanced/explicit_progress
Ansible Support
If you were here last friday you've already seen it, we're now supporting Ansible as a language!
We're very excited to see what can be acomplished by integrating Ansible into the Windmill ecosystem, so feel free to send all your feedback!
https://www.windmill.dev/docs/getting_started/scripts_quickstart/ansible
Ansible Quickstart | Windmill
Windmill Scripts
As we prepare for auto-scaling (EE), we needed more metrics to be held internally such as occupancy_rates at different timelines:
Occupancy rates at different timelines
You can now see occupancy rates for every worker in the 15s/5min/30mins/ever timelines to give you a glimpse of how busy your workers are right now
CLI Updates
We also added better instance management similar to workspaces in the CLI. (wmill instances add/remove, etc)
We added the command:
`
Custom HTTP routes
You can now trigger scripts and flows with custom HTTP routes!
https://www.windmill.dev/docs/core_concepts/http_routing
Custom HTTP routes | Windmill
Windmill supports custom HTTP routes to trigger a script or flow.
Unknown Userā¢4mo ago
Message Not Public
Sign In & Join Server To View
Taking road of replacing
pip with uv šā”
Today, among other improvements, we bring you uv as a replacement for pip-compile. It makes Python lockfile generation much faster and allows you to iterate on your code more quickly.
Our goal is to replace the entire pip with uv, which will make Python development lightning fast and open access to uv's advanced features, so stay tuned for future updates! š
---
Additionally, we have prepared a fallback solution. So if you encounter any problems with python dependencies:
1. Put the # no_uv annotation at the top of your Python script (script-only)
2. Set the environment variable USE_PIP_COMPILE=true (global)
Important Note:
We highly recommend notifying us if any problems occur with uv, as the fallback solution will be removed in the future.
uv: https://github.com/astral-sh/uvUnknown Userā¢4mo ago
Message Not Public
Sign In & Join Server To View
I'm personally very happy about ^. It's the first time we actually spent significant time not adding an actual feature but just working out how to craft an UX that makes windmill both more powerful and simpler at the same time. As Windmill is maturing, you can expect more of those UX improvements that learns from our past experience and put Windmill in a direction to not just be the fastest and most powerful workflow engine, but also the fastest to grok and learn and cater to a wider audience without reducing its caliber.
Are any existing / deployed python script lockfiles regenerated as a part of the upgrade? or does this only take effect when a new version of the script is deployed which i think is when the lock file / dependencies are normally resolved.
Unknown Userā¢4mo ago
Message Not Public
Sign In & Join Server To View
Deno has been updated to 2.0.0 in Windmill š
Unified triggers UX + Simplified Flow Settings UX
We did a big overhaul of the notion of triggers and have been able to improve and unify the triggers UX on the script and flow editor, as well as on the details page of those. The images speaks for themselves. We also took the opportunity to cleanup the settings panel of flows. There was a lot of attention to the details in those and you can notice that we now list the tokens that are attached to a script/flow in the webhook panel and that you can see through badges how many triggers of what kinds are attached to a script/flow + added an intuitive trigger node to flows.
PSA: 1.409.0 -> 1.409.2 have a pretty serious UX bug introduced with 1.409.0 where if you do the interaction of deploying a script/flow that already has a primary schedule, when redeploying them, it may delete the schedule. We strongly recommend upgrading to 1.409.3
.ts need not to be added anymore for relative imports in Typescript (Bun)
After some feedback in #feedback , we realized we had a constraint legacy of deno that wasn't needed anymore. You can now use relative imports in bun of the shape
./dep or ../folder2/dep instead of ./dep.ts and ../folder2/dep.ts. Old style still work and will continue to work