Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the possiblity to do a major release #292

Merged
merged 1 commit into from
Oct 18, 2024

Conversation

leandroberetta
Copy link
Contributor

@leandroberetta leandroberetta commented Oct 18, 2024

This PR adds the ability to do major releases.

Schedule runs are disabled for now.

This PR also sets the 2.0 version for the next Kiali major release on next Monday.

@leandroberetta leandroberetta self-assigned this Oct 18, 2024
NEXT_VERSION=$(python bump.py $RELEASE_TYPE $RELEASE_VERSION)
elif [[ $RELEASE_TYPE == "major" ]]
then
NEXT_VERSION=$(python bump.py "minor" $RELEASE_VERSION)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no idea if this is right or wrong, but this just caught my eye. Since release type is "major" here, shouldn't the bump.py be sent in "major" as its argument value?

Suggested change
NEXT_VERSION=$(python bump.py "minor" $RELEASE_VERSION)
NEXT_VERSION=$(python bump.py "major" $RELEASE_VERSION)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For that case, which is calculate the next version, the bump shouldn't be to 3.0, but to 2.1 instead, for that reason I'm setting a minor bump there.

@leandroberetta leandroberetta merged commit 0624066 into kiali:master Oct 18, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants