There is no way to ignore the Dockerfile due to docker limitation when building an image for a compressed context that reads fro Automatically reset the Dockerfile exception by. Fixed some grammar in v1.1 to v1.2 migration guide (RU) Also added a helper table with all cleanup commands.advanced/cleanup: added info about werf host cleanup GC Fix v1.1 to v1.2 instruction: more correct report usage: pull images before usage Fix v1.1 to v1.2 instruction: wrong images report usage Fix broken quickstart macos instructions What’s new in v1.2/Changelog: cleaning commands rock-solid releases within the minor branch (1.1.x).stable releases within the minor branch (1.1.x).We guarantee backward compatibility between:.We do not guarantee backward compatibility between:.
#What is ea installer cleanup update#
In the case of werf, this means that an update to the next patch release should be smooth and can be done automatically. Patch releases (1.1.0, 1.1.1, 1.1.2) may introduce new features, but must do so without breaking backward compatibility within the minor branch (1.1.x).
![what is ea installer cleanup what is ea installer cleanup](https://help.iris.co.uk/IRIS/ODL/Cleanup4.jpg)
However, it may require running a provided upgrade script. In the case of werf, this means that an update to the next minor release goes smoothly most of the time. Minor releases (1.1, 1.2, etc.) may introduce new global features, but have to do so without significant backward compatibility breaks with a major branch (1.x). In the case of werf, an update to the next major release may require to do a full re-deploy of applications or to perform other non-scriptable actions. It means that major releases (1.0, 2.0) can break backward compatibility. Werf follows a versioning strategy called Semantic Versioning.