v0.8.0

General Changes

• Add metalstack.cloud CLI. (#45) @Gerrit91
• Update dependencies. (#44) @Gerrit91
• include sbom in container image (#41) @mac641

Required Actions

The deployment-base image now comes with Ansible 11. The `ansible-core` was raised from `2.15.4` to `2.18.7`. We did not see any major issues with this update for our roles and playbooks. In case you encounter problems with the update, please adapt your playbooks or file an issue. You can always go back and use the previous release of `metal-deployment-base:v0.7.7` until we found a solution to your issue. Note that Python 2 is not supported anymore. You probably should take a look at the [porting guides](https://docs.ansible.com/ansible/latest/porting_guides/core_porting_guides.html) of Ansible, too.

v0.7.7

General Changes

• Prefer IPv4 dns lookups over IPv6. (#39) @Gerrit91

v0.7.6

General Changes

• Update gcloud and Helm (#36) @Gerrit91
• Create a minimal image without gcloud and save one GB (#38) @robertvolkmann

v0.7.5

General Changes

• Update cloud SDK. (#35) @Gerrit91
• Again hold back ansible-core update, still does not work. (#33) @Gerrit91
• Upgrade actions that still uses Node.js 16 (#32) @robertvolkmann

v0.7.4

General Changes

• Upgrade dependencies (#31) @robertvolkmann
• Add helm-diff to use kubernetes.core.helm (#30) @robertvolkmann

v0.7.3

General Changes

• Downgrade ansible-core to mitigate symlink issue with ansible-galaxy. (#29) @Gerrit91

v0.7.2

General Changes

• Reduce image size (#28) @robertvolkmann

v0.7.1

General Changes

• Update dependencies (#27) @robertvolkmann
• Add jmespath (#26) @robertvolkmann

v0.7.0

General Changes

• Try Jinja2 update (#25) @Gerrit91
• Update deployment components. (#24) @Gerrit91

v0.6.1

General Changes

• Update ansible and install python_jwt. (#22) @Gerrit91