Announcement: Fake.Deploy and FakeLib are deprecated and will be removed

[matthid]

Description

• Fake.Deploy and FakeLib will be deprecated with Fake 5
• It will not be part of the new runner nor will there be support added for the new Runner
• Starting with Fake 6 Fake.Deploy and FakeLib will be removed.

FakeLib

The idea is that FakeLib is split apart into smaller packages in order to:

• Move some APIs faster
• Only pay for what you use

A lot of APIs have already been ported to .NET Core into new Fake 5 modules/nuget packages and we will continue to do so. The transition from FakeLib to the new modules will be a process guided by warning messages (see migration guide). If you encounter problems let us know.

Fake.Deploy

Fake.Deploy was way ahead of its time, however, a lot of time has past and other systems have more than replaced the usefulness of Fake.Deploy. In fact Fake.Deploy can only be used in a very limited set of trusted environments as there is no concept for security or hardening your environments.

On the other hand, Fake 5 can run standalone on a wide range of environments due to .Net Core. Therefore it should be simple to integrate into existing platforms like Chef, Puppet, PowerShell DSC or Azure Resource Templates to name a few.
So starting with Fake 5 it should be easier to run Fake scripts wherever you need them - even without a native Fake.Deploy component.

[matthid]

Closing old announcement, I guess the message has been communicated on all channels :)