Blog

Version 1.0.0 of Cake for Rider has been released.

Highlights of this release include:

• Breaking change Cake for Rider dropped support for all Rider releases before 2020.1
• Added project, file, and live templates
• Added Code Vision support to run tasks directly from the source file
• Added scratch file support
• Added structure view Support

Release Notes

Full details of everything that was included in this release can be seen in the release notes for this version.

Release Video

There is a short video discussing the main aspects of this release.

WhiteSource Renovate is a solution for automating dependency updates in software projects which works (among others) hosted in GitHub (much like dependabot does).

In the new version 24.114.0 Renovate added support for Cake files!

So, as of now it is possible to have pull requests automatically created to update #addin, #tool and #module references in Cake files.

Big thanks go to the people behind WhiteSource Renovate for getting this done so quickly!

Version 0.3.0 of Cake for Rider has been released.

Version 1.1.0 of Cake has been released. Take it for a spin and give us feedback on our discussion board.

This is the first release since our big Cake 1.0 milestone release, and includes new features, improvements and bug fixes to both Cake Scripting and Cake Frosting.

... and more! The full list of changes is listed below.

This release was made possible thanks to the contribution of these awesome members of the Cake community along with Cake team:

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

If you are upgrading from Cake 1.0 and using the .NET tool as we recommend, all you need to do is to update the Cake .NET tool:

See Upgrade instructions for detailed instructions how to upgrade to a newer Cake version and upgrade instructions for previous releases.

The NuGet team at Microsoft introduced a concept known as "Package ID prefix reservation" for packages published on nuget.org, which allows developers to reserve particular package ID prefixes with a specific account/owner and offers a number of features that are described in detail on Microsoft's docs.

One of these features is that packages with a reserved prefix include a visual indicator for NuGet package consumers to identify that the packages they are consuming originate from package owners that have reserved the prefix.