Blog (Page 8)

Cake makes a number of assumptions about files and directories in your project. If you're adding Cake to a brand new project then that isn't a problem, but what happens if you're adding Cake to a 'legacy' project that is already using some of these locations?

Version 1.0.0-rc0001 of Cake has been released

This version is the 110th release of Cake, but the first pre-release of Cake 1.0🎉 In this blog post, we will go through some of the major new features of 1.0, which platforms are supported, and how you can help to get Cake 1.0 released.

We've chosen to release 1.0 as a pre-release to NuGet and Chocolatey, so we and the community can more easily test and ensure that our 1.0 release will be as stable as possible. It will also enable us to see if there are any steps you need to take to adapt your scripts for 1.0, and for us to see if there're any unintended breaking changes, by testing as many addins, modules, and recipes as possible.

See Upgrade instructions for documentation about breaking changes in this release.

While Dependabot currently has no support for Cake, work towards that has already been started.

Using a GitHub Action it is now possible to utilize that work-in-progress to check Cake scripts for outdated references.

When I started working on Cake in 2014, I did it to scratch an itch I had. Fake existed (which has been a tremendous initial inspiration), but I didn't know F# enough to be confident enough to bet our build process on it. A lot has happened since then; .NET has changed, and so has Cake. We've moved from a separate Roslyn and Mono engine to a unified one based on Roslyn. We've added support for C# 6, 7, 8, and just recently 9. In addition to .NET Framework, we've added support for every version of .NET Core, from the early beta to .NET 5. The project has also gone from a single maintainer to nine, which I think is the biggest reason for its success.

Version 0.38.5 of Cake has been released.

In this version, we've just addressed an issue where the upcoming .NET 5 wasn't identified as .NET Core application but .NET 4 / Mono.

This could cause issues with Cake.Tool for example when running .NET Framework executable on non-Windows platforms or scripts reused cross-runtime.

Even though .NET 5 isn't released, we choose to release this as a hotfix so early adopters wouldn't hit this roadblock, but also for our own dogfooding - as we're building Cake with Cake and have started the process of porting Cake to .NET 5.

Contributions were included from:

Full details of everything that was included in this release can be seen below.