Releases: Vanilla-OS/Vib
Releases · Vanilla-OS/Vib
v0.6.0
Breaking changes
- Support for multi-staging introduced, Vib images now requires a top-level
stages
key where you can define one or more stages to build your image, all the definitions now must be placed in the stages section, please have a read - The -
expose
key is now takes a string, this allows mapping like:8080/tcp
- Support for
env
key added, this takes a map of strings:
envs:
MY_ENV: my_value
MY_OTHER_ENV: my_other_value
Full Changelog: v0.5.0...v0.6.0
v0.5.0
- Support for remote modules is landed, now you can define 3rd party modules in your
includes
modules by pointing to the direct URL (e.g.https://my-repo.com/modules/node.yaml
) or by using thegh
pattern (e.g.gh:my-org/my-repo/modules/python.yaml
) Read more - The
apt
module has a newoptions
key to tweak the APT's behavior Read more - The
vib compile
command now uses the system podman/docker storage instead of a custom one, making Vib-compiled images available from container managers and tools like distrobox and toolbx
Full Changelog: v0.4.0...v0.5.0
v0.4.0
What's Changed
- adds support for
Entrypoint
in the recipe - adds support for
Expose
in the recipe
Full Changelog: v0.3.3...v0.4.0
v0.3.3
What's Changed
Full Changelog: v0.3.2...v0.3.3
v0.3.2
What's Changed
- fix: typo in README by @IlgazC in #6
- feat/ci: bump actions/checkout to v4 by @kbdharun in #7
- Validate checkshum for downloaded files excluding git files by @arejula27 in #9
- feat: add module support by @axtloss in #12
- feat/ci: bump actions/setup-go to v5 by @kbdharun in #13
- fix:[closes #14] specify api version by @axtloss in #15
New Contributors
- @IlgazC made their first contribution in #6
- @kbdharun made their first contribution in #7
- @arejula27 made their first contribution in #9
- @axtloss made their first contribution in #12
Full Changelog: v0.3.1...v0.3.2
v0.3.1
The new includes
module type replaces the gen-modules
type which is now deprecated and will be removed in the future.
This new special module type allows including modules in a more flexible and managed way, by listing them directly in the recipe, this allow to easily re-order modules without having to change the file name, plus the ability to import modules from different paths using just 1 module.