Skip to content

Add check to validate the value of PREVIOUS_RELEASE_TAG in release-notes-tools #12278

Open
@chandankumar4

Description

@chandankumar4

What steps did you take and what happened?

Add check to validate PREVIOUS_RELEASE_TAG that it should contains rc or beta in the provided value.

For example

  1. Generating notes for rc tag
    RELEASE_TAG=v1.7.x-rc.1 PREVIOUS_RELEASE_TAG=tags/v1.7.x-rc.0 make release-notes
  2. Generating notes for beta tag
    RELEASE_TAG=v1.7.x-beta.1 PREVIOUS_RELEASE_TAG=tags/v1.7.x-beta.0 make release-notes

What did you expect to happen?

Validate should ensure that PREVIOUS_RELEASE_TAG is in correct format.

Cluster API version

v1.10

Kubernetes version

No response

Anything else you would like to add?

No response

Label(s) to be applied

/kind bug
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.

Metadata

Metadata

Assignees

Labels

help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/bugCategorizes issue or PR as related to a bug.priority/backlogHigher priority than priority/awaiting-more-evidence.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions