we migrated the cloud to ARM instances, you shouldn't see any changes but let us know if you do
SCongrats on the big change, are you seeing performance improvements? or was it mostly a cost thing?
MI'm super curious as well 
and congrats on succesfull migration
and congrats on succesfull migration
R3 reasons:
- cost
- performance
- aligning with what we recommend our own customers to do
- cost
- performance
- aligning with what we recommend our own customers to do
ROne thing we weren't able to do was to make nsjail work with the bottlerocket images and for some reasons we had DNS issues with al2023 so we're still on al2 for the cloud but we migrated our dedicated instances to bottlerocket and can thus also enjoy groupv2 which has a better oom killer wrt to filesystem kernel cache
RThe args in the runs page are now directly synced with the url fragment/anchor, meaning you get sharable urls with pre-filled args automatically by just sharing your current URL. e.g:
It also works well with back/forward and browser history.
We also improved the whole way we dealt with the browser history and back/forward should work better in more places. We also did some nits such that editing a script from a run detail page will now prefill the test args with the jobs args
https://app.windmill.dev/scripts/get/dae90ddc108ce257?workspace=windmill-labs#disable_automatic_renewal=false&send_invoice_directly=true&discount_duration=%221+year%22&discount=0&frequency=%22monthly%22&seats=1&vcpus=2&plan=%22selfhosted_ee%22&stripe_customer_data=%7B%22label%22%3A%22New+stripe+customer%22%2C%22email%22%3A%22%22%2C%22address%22%3A%7B%22line1%22%3A%22%22%2C%22postal_code%22%3A%22adsadas%22%2C%22state%22%3A%22%22%2C%22city%22%3A%22%22%7D%2C%22tax_info%22%3A%7B%22value%22%3A%22%22%7D%7D&is_quote=false&contact_email=%22bar%40acme%22&company_name=%22acme%22It also works well with back/forward and browser history.
We also improved the whole way we dealt with the browser history and back/forward should work better in more places. We also did some nits such that editing a script from a run detail page will now prefill the test args with the jobs args
HWe have a new type of input: oneOf, that displays an option between multiple objects.
They can be used in TypeScripts, flows and any UI-built schema.
Changelog: https://www.windmill.dev/changelog/oneof-inputs
Docs: https://www.windmill.dev/docs/core_concepts/json_schema_and_parsing#oneof
They can be used in TypeScripts, flows and any UI-built schema.
Changelog: https://www.windmill.dev/changelog/oneof-inputs
Docs: https://www.windmill.dev/docs/core_concepts/json_schema_and_parsing#oneof
Hexample of oneOf input in flows
HWe have a new component on the App Editor: Navbar
It facilitates control over an app by changing its ctx.query, enabling:
- Changing the behavior of the app by manipulating the query arguments and hash of the URL.
- Opening an external URL in a new tab.
- Opening another Windmill app, which allows for creating embedded apps where the user navigates between several of your Windmill apps.
Changelog: https://www.windmill.dev/changelog/navbar
Docs: https://www.windmill.dev/docs/apps/app_configuration_settings/navbar
It facilitates control over an app by changing its ctx.query, enabling:
- Changing the behavior of the app by manipulating the query arguments and hash of the URL.
- Opening an external URL in a new tab.
- Opening another Windmill app, which allows for creating embedded apps where the user navigates between several of your Windmill apps.
Changelog: https://www.windmill.dev/changelog/navbar
Docs: https://www.windmill.dev/docs/apps/app_configuration_settings/navbar
RFlow status viewer change:
- improved dark mode theme
- you can now pick the iteration to view from directly in the graph
- for branchall, branchone, while loop and forloops, the status of the branch/iteration is now displayed in the top node. For instance, for branchone, it will also allow you to know which branch was picked
- now the colors of the forloop itself corresponds to the entire forloop status and not the iteration. The iteration status is in the "Do one iteration" block
- You can pick the iteration to view the detail of directly in the forloop
- The forloop detail page now list every iteration status, even if you have a thousand one without having to load them all
- The nodes such as forloop and branchall that collect multiple results now show separately the collection of the results of all subflows and the result of the selected branch/iteration
- improved dark mode theme
- you can now pick the iteration to view from directly in the graph
- for branchall, branchone, while loop and forloops, the status of the branch/iteration is now displayed in the top node. For instance, for branchone, it will also allow you to know which branch was picked
- now the colors of the forloop itself corresponds to the entire forloop status and not the iteration. The iteration status is in the "Do one iteration" block
- You can pick the iteration to view the detail of directly in the forloop
- The forloop detail page now list every iteration status, even if you have a thousand one without having to load them all
- The nodes such as forloop and branchall that collect multiple results now show separately the collection of the results of all subflows and the result of the selected branch/iteration
HFlows now have versions just like scripts and apps.
We have also introduced:
- Redeploy of Scripts, Flows, Apps from past version.
- Fork Scripts, Flows, Apps from past version.
- Add deployment messages for Scripts and Flows.
Changelog: https://www.windmill.dev/changelog/flow-versioning
We have also introduced:
- Redeploy of Scripts, Flows, Apps from past version.
- Fork Scripts, Flows, Apps from past version.
- Add deployment messages for Scripts and Flows.
Changelog: https://www.windmill.dev/changelog/flow-versioning
RWindmill now pre-bundle Typescript (Bun) scripts and cache them on S3 and locally at deployment time. Furthermore, if a bun script is ran while not being pre-bundled, it will be re-bundled.This will improve cold start time and memory usage of all bun scripts, in particular for scripts with many/heavy imports and relative imports. We also did improvements for non-deployed scripts using better caching strategies for the dependency cache. You cannot do any faster than running a pre-bundled script aside from having the script being already running which is what dedicated workers are made for. This makes windmill the fastest platform to run typescript. We have improvements in the work to improve the DX and versatility of dedicated workers as well coming soon.
HWe have a new helper function within scripts:
Dynamic Select helps you to create a select field with dynamic options:
- Options within the select field can dynamically change based on input arguments.
- Support for TypeScript and Python.
- Conditional logic within the function to filer and sort select options based on specified conditions.
Changelog: https://www.windmill.dev/changelog/dynamic-select
DynSelect_Dynamic Select helps you to create a select field with dynamic options:
- Options within the select field can dynamically change based on input arguments.
- Support for TypeScript and Python.
- Conditional logic within the function to filer and sort select options based on specified conditions.
Changelog: https://www.windmill.dev/changelog/dynamic-select
Dynamic Select is an helper function within scripts that allows you to create a select field with dynamic options.
RWe've made our runtime that we've called "REST" and "nativets" supports npm packages and relative imports! There is now no difference in the syntax of typescript/bun scripts and native scripts. Native scripts still only support a subset of what node support (just the fetch operation) but many npm packages can still be used because that's all they use under the hood (for instance, windmill-client and axios).
How to activate ? Just add
We've also changed the default docker-compose/helm template to go from 4 small native workers with each 1 subworker to 1 bigger native worker with 8 subworkers as it performed better in our benchmarks. If you need more throughput, simply increase the replicas of the native workers, don't increase the number of subworkers past 8 as the interleaving will result in lower throughput.
This is a huge improvement as you can now make our
How to activate ? Just add
//nativeWe've also changed the default docker-compose/helm template to go from 4 small native workers with each 1 subworker to 1 bigger native worker with 8 subworkers as it performed better in our benchmarks. If you need more throughput, simply increase the replicas of the native workers, don't increase the number of subworkers past 8 as the interleaving will result in lower throughput.
This is a huge improvement as you can now make our
native//nativenativeWe fixed one of the most annoying bug of the frontend code editor of apps, types are no more overly narrowed to their literal types which mean you do not get erroneous squiggly error anymore for comparison and assignments, before vs after:
Rcontainer group fields are now mutable internally, so you can start building reusable component groups with more stateful inner logics
RNew options for approval/suspend steps: Continue on disapproval/timeouts
Instead of failing the flow and bubbling up the error, continue to the next step which would allow to put a branchone right after to handle both cases separately. If any disapproval/timeout event is received, the resume payload will be similar to every error result in Winmdill, an object containing an
Instead of failing the flow and bubbling up the error, continue to the next step which would allow to put a branchone right after to handle both cases separately. If any disapproval/timeout event is received, the resume payload will be similar to every error result in Winmdill, an object containing an
error
RNew option for flow error handlers: recover the flow if
recover: true
RWe added a vim mode to the code editors
HOn the app editor, you can now hide left, right and botom panels with special button or shortcuts
https://www.windmill.dev/changelog/hide-show-app-panels
https://www.windmill.dev/changelog/hide-show-app-panels
Hide panels on App Editor with buttons and shortcuts.
HScripts and flows can now be triggered by the delivery of an email!
We'll be showing more today at 6 p.m. CET in our first weekly demo.
https://www.windmill.dev/changelog/email-triggers
https://www.windmill.dev/docs/advanced/email_triggers
We'll be showing more today at 6 p.m. CET in our first weekly demo.
https://www.windmill.dev/changelog/email-triggers
https://www.windmill.dev/docs/advanced/email_triggers
HRMajor: 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
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
Ryou can now edit directly the yaml of flows within the flow editor
RMajor: windmill CLI (wmill) installable with npm and nodeJs compatible
We've made the CLI more accessible by being directly installable from npm:
There are no changes, the command is still wmill, and you will still be able to upgrade it with
One focus of this quarter is to improve the on-boarding experience and reduce the steep curve to learn windmill.
We've made the CLI more accessible by being directly installable from npm:
npm install -g windmill-cliThere are no changes, the command is still wmill, and you will still be able to upgrade it with
wmill upgradedeno uninstall wmill && npm install -g windmill-cliOne focus of this quarter is to improve the on-boarding experience and reduce the steep curve to learn windmill.
GitHub
Contribute to windmill-labs/windmill-sync-example development by creating an account on GitHub.
Ryou can now easily change the id of steps in flows and it will modify every step inputs that depend on it automatically
RWe've improved the vscode extension handling of relative paths:
- On python it will detect that you're using relative paths and warn you that
- 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
- On python it will detect that you're using relative paths and warn you that
wmill sync push- 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
RWe fixed paste on macos on the vscode extension (you will need to update your instance to latest)
RIf 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.
PHey! 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
WAnsible 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
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
Windmill Scripts
RAs 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:
`
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:
`
HCustom HTTP routes
You can now trigger scripts and flows with custom HTTP routes!
https://www.windmill.dev/docs/core_concepts/http_routing
You can now trigger scripts and flows with custom HTTP routes!
https://www.windmill.dev/docs/core_concepts/http_routing
Windmill supports custom HTTP routes to trigger a script or flow.
PTaking road of replacing 
Today, among other improvements, we bring you
Our goal is to replace the entire
---
Additionally, we have prepared a fallback solution. So if you encounter any problems with python dependencies:
1. Put the
2. Set the environment variable
Important Note:
pipuvToday, among other improvements, we bring you
uvpip-compileOur goal is to replace the entire
pipuvuv's---
Additionally, we have prepared a fallback solution. So if you encounter any problems with python dependencies:
1. Put the
# no_uv2. Set the environment variable
USE_PIP_COMPILE=trueImportant Note:
We highly recommend notifying us if any problems occur with, as the fallback solution will be removed in the future.uv
uvI'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.
DAre 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.
RDeno has been updated to 2.0.0 in Windmill 
RUnified 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
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
R.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
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../folder2/dep./dep.ts../folder2/dep.tsOverride warning on deploy
Now windmill will warn you if you try to overwrite a script, flow or app deployed by somebody else while you have been editing. It will also show a diff
Now windmill will warn you if you try to overwrite a script, flow or app deployed by somebody else while you have been editing. It will also show a diff
RMany UX improvements for the flow builder
We have lots of nice changes we haven't announced but here is one bulk changelog for the flow editor:
- If you write a static string that looks like an expr we will offer to make it an expr as a TAB
- you can now connect to nodes directly using a plug system similar to the nodes for apps
- when you type an expr, the right panel will filter the possibilties based on what you type
- the right panel, select expr and object viewer went through a major aesthetic refactor
Most of this work has been led by @Guilhem, our new UX engineer. It puts us much closer to being better for both power-users and less technical users by having a simple yet very powerful UX that doesn't dumb down the product
We have lots of nice changes we haven't announced but here is one bulk changelog for the flow editor:
- If you write a static string that looks like an expr we will offer to make it an expr as a TAB
- you can now connect to nodes directly using a plug system similar to the nodes for apps
- when you type an expr, the right panel will filter the possibilties based on what you type
- the right panel, select expr and object viewer went through a major aesthetic refactor
Most of this work has been led by @Guilhem, our new UX engineer. It puts us much closer to being better for both power-users and less technical users by having a simple yet very powerful UX that doesn't dumb down the product
RExpandable subflows directly in flows
Long requested feature. You can now expand flow steps directly inside the flows in all flows screen (flow editor, flow status, etc) making it a LOT easier to work with nested flows.
Long requested feature. You can now expand flow steps directly inside the flows in all flows screen (flow editor, flow status, etc) making it a LOT easier to work with nested flows.
RWeekly 3: https://youtu.be/w-K8mzUfpIs (HD still processing)
- EU cluster
- Kafka
- Extending cron support
- Workspace specific critical alerts
- FileUpload support for our AI generated hub scripts
- new pricing page presentation
- EU cluster
- Kafka
- Extending cron support
- Workspace specific critical alerts
- FileUpload support for our AI generated hub scripts
- new pricing page presentation
YouTubeWindmill
EU cluster
Kafka
Extending cron support
Workspace specific critical alerts
FileUpload support for our AI generated hub scripts
new pricing page presentation
Kafka
Extending cron support
Workspace specific critical alerts
FileUpload support for our AI generated hub scripts
new pricing page presentation
RThe iteration picker for flows was not super practical for flows that were still running. Now it both locks the iteration picked and will loads all the substeps at any depth correctly, and running steps won't interfere with it.
HWe have introduced a new pricing https://www.windmill.dev/pricing
Instead of vCPUs, we are now basing pricing on compute units (a 2GB worker used for a full month). Workers have a size (small, standard, large) based on their memory limit (<=1, (1-2], >2) and each worker size gets a compute unit (0.5, 1, 2)
With this new approach, you can now get rid of setting vCPU limits which is an anti-pattern in favor of only setting them as requests not to limit unnecessarily the compute power of your workers
Apart from that, seats and discounts for non-profits and SMBs still exist
Instead of vCPUs, we are now basing pricing on compute units (a 2GB worker used for a full month). Workers have a size (small, standard, large) based on their memory limit (<=1, (1-2], >2) and each worker size gets a compute unit (0.5, 1, 2)
With this new approach, you can now get rid of setting vCPU limits which is an anti-pattern in favor of only setting them as requests not to limit unnecessarily the compute power of your workers
Apart from that, seats and discounts for non-profits and SMBs still exist
Rrefreshable components are now cancellable directly on the app
