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

🌱 Prepare main branch for v0.6 development #416

Merged
merged 1 commit into from
Aug 27, 2024

Conversation

furkatgofurov7
Copy link
Contributor

@furkatgofurov7 furkatgofurov7 commented Aug 27, 2024

What this PR does / why we need it:
Prepares the main branch for v0.6 development.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:
We need to prepare a main branch by updating our e2e tests and adding a new upcoming provider version in metadata.yaml in advance before cutting a new CAPRKE2 minor release. This needs to be done always, right after we cut a new minor release.

Related to and follows instructions from: #373

Checklist:

  • squashed commits into logical changes
  • includes documentation
  • adds unit tests
  • adds or updates e2e tests

@furkatgofurov7 furkatgofurov7 added area/build-and-release Indicates issue or PR related to build or release kind/release-blocking Issues or PRs that need to be closed before the next release labels Aug 27, 2024
@furkatgofurov7 furkatgofurov7 merged commit 7b6bbba into rancher:main Aug 27, 2024
6 checks passed
@furkatgofurov7 furkatgofurov7 deleted the prepare-main-branch branch August 27, 2024 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build-and-release Indicates issue or PR related to build or release kind/release-blocking Issues or PRs that need to be closed before the next release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants