chore: Add release please action

[shubham2g]

chore: Add release please action

Jira Ticket#https://jira.nutanix.com/browse/NCN-104689

[mhrabovcin]

@shubham2g this requires also a github action workflow. https://github.com/googleapis/release-please-action Please see some example in other NKP repos.

[shubham2g]

Hi @mhrabovcin Created Github Action Workflow, kindly review.

[mhrabovcin]

Remove this secret usage.

[mhrabovcin]

@shubham2g the action and new files needs some adjustments:

• https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md#initial-version - the initial version needs to be set to the last release version
• https://github.com/googleapis/release-please-action?tab=readme-ov-file#advanced-release-configuration - manifests driven releases require different action inputs
• This is a public repo which don't have access (correctly) to the MESOSPHERECI_USER_TOKEN. We need to use a generated token.

Here is an example of release please action for a public repo - https://github.com/nutanix-cloud-native/cluster-api-runtime-extensions-nutanix/blob/main/.github/workflows/release-please.yml

[mhrabovcin]

Use a public runner.

[mhrabovcin]

What are these options doing?

[shubham2g]

If release-please includes GHCR as part of its release process (e.g., for publishing containerized artifacts or versions), this configuration is essential for authentication. However, if it does not involve pushing or pulling artifacts from GHCR (e.g., it only handles GitHub releases and tags), this block is unnecessary. Since I’m uncertain about the current need for GHCR, it might be safe to omit this block for now and add it later if GHCR interaction becomes required.

[mhrabovcin]

We've chatted via slack - these input values are not supported by the action.

[mhrabovcin]

This shouldn't be included - we want to ru manifest release type.

Suggested change

release-type: go

[mhrabovcin]

Suggested change

	env:
	GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
	env:
	GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

I don't think that this is necessary.

[mhrabovcin]

Suggested change

	git tag -d v${{ steps.release.outputs.major }} || true
	git tag -d v${{ steps.release.outputs.major }}.${{ steps.release.outputs.minor }} || true
	git push origin :v${{ steps.release.outputs.major }} || true
	git push origin :v${{ steps.release.outputs.major }}.${{ steps.release.outputs.minor }} || true
	git tag -a v${{ steps.release.outputs.major }} -m "Release v${{ steps.release.outputs.major }}"
	git tag -a v${{ steps.release.outputs.major }}.${{ steps.release.outputs.minor }} -m "Release v${{ steps.release.outputs.major }}.${{ steps.release.outputs.minor }}"
	git push origin v${{ steps.release.outputs.major }}
	git push origin v${{ steps.release.outputs.major }}.${{ steps.release.outputs.minor }}
	git tag -a ${{ steps.release-please.outputs.tag_name }} -m "Release ${{ steps.release-please.outputs.tag_name }}"
	git push origin ${{ steps.release-please.outputs.tag_name }}

[mhrabovcin]

Suggested change

	env:
	GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

[shubham2g]

Removed.

[mhrabovcin]

Suggested change

	tags:
	- 'v*'

This action should run on branches.