Add new workflow to bump version and create Github Release

[mrodm]

Add a new workflow that is intended to be run once all branches for a release are already merged in the main branch.

This workflow is going to:

• Set the right version in metadata.json
• Create a Github Release with the corresponding release notes (auto-generated).

In a future step, it could be set here the step to publish the tgz into puppet forge.

Github actions used:

• https://github.com/marketplace/actions/set-json-field : Set the new value in the field version
• https://github.com/marketplace/actions/get-json-property : Get the current value of the json
• https://github.com/marketplace/actions/add-commit : Commit and push changes
• https://github.com/marketplace/actions/gh-release : Create Github release

[mrodm]

Should this be considered as a secret to avoid spam?
as this is a public repo...

[oscarsj]

probably, i think security advisor will raise a warning with this

[oscarsj]

I see the idea behind this workflow is to manually set the version. Shouldnt we have the version autoamtically managed ? Commit it in a version file in the repo and just bump it (semver or with other methods)

[mrodm]

I see the idea behind this workflow is to manually set the version. Shouldnt we have the version autoamtically managed ? Commit it in a version file in the repo and just bump it (semver or with other methods)

The version is already in the repository in the metadata.json file. That file is the one used by the pdk tool to build the artifact and use the version from there. If we create another file for version, it is going to be duplicated.

[oscarsj]

I see the idea behind this workflow is to manually set the version. Shouldnt we have the version autoamtically managed ? Commit it in a version file in the repo and just bump it (semver or with other methods)

The version is already in the repository in the metadata.json file. That file is the one used by the pdk tool to build the artifact and use the version from there. If we create another file for version, it is going to be duplicated.

ok then, let use that file to do an automated versioning instead of requiring the version to be an input of the workflow, that way we can autoamtically trigger a release on other events , such as PR merged

[Yermanaco]

cool workflow! FMPOV (agreed with Oscar) bumping version automatically (getting current version from json file) could be more useful rather than set it as an input.

[Yermanaco]

maybe makes more sense do it next time