It's finally time! After nearly 3 years as an experiment, we're excited to announce that today, remote Taskfiles have been made generally available. No more setting flags or config to enable it. It is enabled by default and will continue to work seamlessly with your existing remote taskfiles.
Did you know that GitHub has a special program to fund security in open source? It's the GitHub Secure Open Source Fund. We were selected to participate in session 4 that happened in May 2026 and it was really special for us.
Do you know that you can use Task without really needing to install it?
If you work with Go, you probably depend on external binaries like linters, code generators and... Task.
The v3.47.0 release is here, and it brings two exciting new features to Task. Let's take a closer look at them!
When I started Task back in 2017, one of my biggest goals was to build a task runner that would work well on all major platforms, including Windows. At the time, I was using Windows as my main platform, and it caught my attention how much of a pain it was to get a working version of Make on Windows, for example.
Task has always had variables, but even though you were able to define them using different YAML types, they would always be converted to strings by Task. This limited users to string manipulation and encouraged messy workarounds for simple problems. Starting from v3.37.0, this is no longer the case! Task now supports most variable types, including booleans, integers, floats and arrays!
Lately, Task has been growing extremely quickly and I've found myself thinking a lot about the future of the project and how we continue to evolve and grow. I'm not much of a writer, but I think one of the things we could do better is to communicate these kinds of thoughts to the community. So, with that in mind, this is the first (hopefully of many) blog posts talking about Task and what we're up to.
