CEKit 3.6.0 released

      1 min read        release

This is another minor CEKit release. It contains fixes for a few bugs reported as well as some general improvements. You can see full release notes here. Below you can find highlights of this release. Alpine Linux support Alpine Linux support was added. Even before you could base on Alpine Linux image, but this time you can also install packages using the APK package manager. Please give it a try if you like this distro and let us know if you find any issues.

CEKit 3.5.0 (and others) released

      3 min read        release

This is a special release day actually. Today we released 3 versions of CEKit. Two bugfixes and one scheduled release. Let me go through these. CEKit 3.2.1 and 3.3.2 bugfix releases Note These releases are available only on PyPi, there will be no RPMs prepared for these versions. To support Middleware teams on the route to continuous development (CI/CD) and not to interrupt their current workflows at thea same time I decided to backport changes from the 3.

CEKit 3.4.0 released

      2 min read        release

After almost a month after last release we have now a fresh one that just came out! Let me introduce CEKit 3.4.0 which is focused on adding support for multi-stage builds. You can read the full changelog on GitHub. Multi-stage build support was added Note Although the support for multi-stage builds is already baked, please consider this a tech-preview feature until 3.5 is out. If you are interested in multi-stage builds, we encourage you to test this feature and report all issues you will find.

CEKit 3.3.1 released

      2 min read        release

We have another exciting announcement in the pocket: the 3.3.1 version was just released! Note Version 3.3.0 was never released due to the fact that we encountered issues with PyPi which made it impossible to push version 3.3.0 again. There are no changes in the code between version 3.3.0 and 3.3.1. Say hi to 3.3.1! This release focuses on documentation improvements, especially in for modules.

Module naming and versioning guidelines

      2 min read        guideline

As part of the upcoming 3.3.0 release preparation — module documentation was updated in several places. Among other things module naming and versioning pages were added. Below you can find a summary of our suggestions. You can already browse the development version of the documentation. It will become the main documentation after the 3.3.0 release. Note You are free to use your own module name and versioning scheme, but standardizing on the same format will make it easier to reuse modules prepared by someone else.

CEKit 3.2.0 is out!

      2 min read        release

Here we are with the next 3.2.0 release! This is generally a bugfix release with some additional usability improvements. Full changelog can be found here, below you can see highlights of this release. Better macOS support As part of development we added support for executing tests on macOS platform in our CI. This should make the macOS experience better. In the future we plan to make CEKit installation easier on this platform as well.

CEKit 3.1.0 released

      2 min read        release

After 3.0.0 release we decided make our release cycle faster. We’re not afraid of new version numbers, you shouldn’t be too 😏 From now on you can expect new minor releases come out faster. These will be less feature-packed but on other hand this will let us shorten the time between a bug/feature report and the release containing the fix. Above introduction would be meaningless without a release, so here it is!

CEKit 3.0.1 released

      1 min read        release

After initial 3.0.0 release we’ve done earlier this month we’ve gathered feedback and we found that some issues warrant a new bugfix release. Changes Learn more below about these fixes. Fixes in packages and modules installation in overrides In case packages or modules were defined only in overrides (the main image descriptor did not have any mention of packages or modules), these were ignored. This was fixed and now you can have a pretty much empty image descriptor and define your content in modules only.

CEKit 3.0.0 released

      3 min read        release

Phew, that was quite some work, but we made it finally! We’re very happy to announce immediate availability of CEKit 3.0.0! Before we dive into details we would like to thank following people for their help on the release (no particular order) Jonathan Dowland; bug reports, testing, feedback Ken Wills, testing, feedback Nick Cross; contributions David Ward; testing, feedback It also a great time to thank David Becvarik, previous CEKit project leader, for his dedication to make CEKit a better project 👏 Thank you and good luck in your new role!

Module merging changes

      3 min read        3.0 · development

We are very close to release CEKit version 3.0. This is a great time to discuss one of the biggest changes we made in the codebase in preparation for 3.0: the module merging process rewrite. Old style merging Since early days of CEKit all modules were processed and merged internally. What does it mean? Let’s imagine we have an image descriptor that requires a few modules to install. These modules can define anything what is available in the module descriptor.