**Weekly 3**: https://youtu.be/w-K8mzUfpIs (HD still processing) - EU cluster - Kafka - Extending cr
Weekly 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
Windmill
YouTube
Windmill Weekly 3
EU cluster
Kafka
Extending cron support
Workspace specific critical alerts
FileUpload support for our AI generated hub scripts
new pricing page presentation
16 Replies
The 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.
We 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

refreshable components are now cancellable directly on the app
Unknown User•4mo ago
Message Not Public
Sign In & Join Server To View
Multiselects can now take labeled values in apps:

you can now enforce dark/light mode on apps (also help with quickly checking rendering on both themes)
small changelog for aggrid fanatics, you can make your app using aggrid behave a lot better by setting the newly exposed rowIdCol to an id that is stable in your rows:. It allows AgGrid to compute the best re-display of the table on changes. If you don't it will use our auto-generated ids like before but there are cases where it's less optimal

App custom URL
Cloud and enterprise users can now set a custom public URL for their app!
https://www.windmill.dev/changelog/app-custom-url
https://www.windmill.dev/docs/apps/public_apps#custom-url

more native docker jobs support
With the new
# docker
annotation, windmill will manage the container started from your bash job for you, including piping the logs, monitoring memory and super importantly stopping container on job cancel or worker kill for you. That's one step closer to have windmill support managing external jobs on k8s/ecs/nomad/swarm directly.
Issues with apps released between Windmill 1.436.0 (5 days old) -> 1.437.0: Update to >= 1.437.1
Newly deployed apps with Windmill on those versions will see their frontend scripts not running. The mistake is related to a performance improvement we did.
You just have to update to Windmill version >= 1.437.1 or latest helm chart. It doesn't impact apps that were deployed prior to those versions and it only impact frontend scripts.
Big apologies 🙇♂️
C# on Windmill!
Starting on v1.438.0 you can write and run C# on Windmill. For package management, just specify dependencies at the top of the file and they will be automatically handled by NuGet. Go try it out!
Changelog: https://www.windmill.dev/changelog/csharp
Docs: https://www.windmill.dev/docs/getting_started/scripts_quickstart/csharp

Interactive Slack Approval Steps
Effortlessly approve or reject flow steps directly within Slack! This feature includes support for form inputs, dynamic enums, default arguments and includes a Python and Typescript helper function.
Approvers can now complete the process without leaving Slack, eliminating the need to switch to a browser.
Changelog: https://www.windmill.dev/changelog/slack-approval-steps
Docs: https://www.windmill.dev/docs/flows/flow_approval#slack-approval-step
https://cdn.discordapp.com/attachments/1260616311994712074/1327279249605918730/slack_approval_short.mp4?ex=67827ca0&is=67812b20&hm=6e1090f03f2bade4933996932c8610710eb03f905388f1aa3dd23f9d3c08ad27&
Interactive Slack Approval Steps
Approve or reject flow steps directly from Slack with support for form inputs
Suspend & Approval / Prompts | Windmill
Flows can be suspended until resumed or canceled event(s) are received. This
Workspace Colors
You can now color-code your workspaces to visually distinguish between different workspaces, especially when the side-bar is collapsed. This can be particularly useful to differentiate between prod/test workspaces.
Changelog: https://www.windmill.dev/changelog/workspace-color
Docs: https://www.windmill.dev/docs/core_concepts/workspace_settings#workspace-color

You can watch our weekly lives on our Youtube channel
Today's keynote: https://www.youtube.com/watch?v=8tOpodhrg68
Windmill
YouTube
Windmill Weekly #7
00:00 Waiting
03:26 Alex: Ongoing work on Microsoft Teams integration
06:09 Alex: Signing commits with GPG when using git-sync
08:15 Hugo: on_behalf_of for scripts and flows
11:05 Etienne: Integration with Svix for simple webhook creation and management
11:45 Q&A
Support for multiple python runtime versions 🐍
Starting from Windmill 1.449.0 you can select python version you would like to use in your scripts.
It is done by putting annotation to the python script. Just add this line on top of your file:
#py312
You can also set INSTANCE_PYTHON_VERSION
to use specific version globally.
Already deployed scripts will always run 3.11 unless redeployed ☝️
Supported versions are: 3.10, 3.11, 3.12 and 3.13Changelog: https://www.windmill.dev/changelog/select-python-version Docs: https://www.windmill.dev/docs/getting_started/scripts_quickstart/python#select-python-version
Release 1.458.0 and current latest
TL;DR: Jobs V2 format and migration may take more time than usual if high number of jobs > 1M
In release 1.458.0 (not released yet, will be by EOD) we are migrating the format of our jobs in the database (format was 1.5yo) in a non-breaking, back-compatible, no downtime needed way. This format will allow us to improve performance as well as unblock us on some long-awaited features.
You can upgrade as usual, but if you have more than 1M jobs, the migration may take around 25mins/Million of jobs. It will not block the cluster and existing workers and jobs will continue to work as usual but new workers and apps will wait for the automatic migration to be fully complete before being able to fully start.