[admin] Validate version format in release workflow

[mx-psi]

We don't do any validation on the version introduced for the prepare-release workflow, but we have some restrictions on the version format as documented here:

opentelemetry-collector/.github/workflows/prepare-release.yml

Lines 3 to 22 in 2c132fa

	on:
	workflow_dispatch:
	# Determine the version number that will be assigned to the release. During the beta phase, we increment
	# the minor version number and set the patch number to 0.
	inputs:
	candidate-stable:
	required: true
	description: Release candidate version (stable, like 1.0.0-rc4). Don't include `v`.
	current-stable:
	required: true
	description: Current version (stable, like 1.0.0-rc3). Don't include `v`.
	candidate-beta:
	required: true
	description: Release candidate version (beta, like 0.70.0). Don't include `v`.
	current-beta:
	required: true
	description: Current version (beta, like 0.69.1). Don't include `v`.

We should add some validation to make the release workflow fail fast if the tags don't match the expected schema.

Relates to #7576

[Abhishek-569]

I want to work on this.

[mx-psi]

Assigned to you @Abhishek-569 :)

[Abhishek-569]

Thanks. @mx-psi is there any place to learn on how to add validation in a workflow?

[mx-psi]

Github does not have any form of input validation built-in, so you will have to add a new step to this job

opentelemetry-collector/.github/workflows/prepare-release.yml

Line 27 in 2c132fa

steps:

and write a small bash script to check for the format (e.g. by using a regular expression)

[Abhishek-569]

okay thanks.

[Abhishek-569]

Please check this PR #8135 for this issue. @mx-psi

[mx-psi]

We ran into this on v0.82.0 as well

[serverless-mom]

I'd like to work on this.

[Sanket-0510]

Hey @mx-psi I would like to take over this issue, I'll try to open PR very you assign this to me for sure.

[mx-psi]

Thanks for fixing this @Sanket-0510 !

[Sanket-0510]

Thanks for fixing this @Sanket-0510 !

My pleasure ❤️❤️✨