the release automation should be enhanced for the community to include automatic tags and release notes

[johndietz]

What is your feature idea?

kubefirst internal release automation that produces release notes and a tag during the release process should be promoted to the community open source platform.

Why is it needed?

when a product releases a chart, it's traceable to the codebase through the container's naming convention including the sha1, however a more prominent approach for trunk based development is to tag the main branch of the repository at the point of release, generating a release and release notes to host in github or gitlab ecosystems. they could obviously add this themselves, but i think it would be appreciated by most to instead remove if they want to opt out. i think we should be promoting this as a standard in our example ci starting point.

Is this missing feature preventing you from using kubefirst?

• Yes

Code of Conduct

• I agree to follow this project's Code of Conduct