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

chore(main): release 0.6.0 #107

Merged
merged 1 commit into from
Jun 1, 2023
Merged

chore(main): release 0.6.0 #107

merged 1 commit into from
Jun 1, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Apr 24, 2023

🤖 I have created a release beep boop

0.6.0 (2023-06-01)

Features

Bug Fixes

  • return helm output (95c32a7)
  • Wait until observedGeneration of the capi cluster is increased in cluster upgrade (58b6325), closes #57

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot changed the title chore(main): release 0.2.0 chore(main): release 0.5.5 Apr 30, 2023
@github-actions github-actions bot force-pushed the release-please--branches--main branch from ce3b194 to 242afe5 Compare April 30, 2023 19:23
@github-actions github-actions bot force-pushed the release-please--branches--main branch 2 times, most recently from 835d7a0 to 6f119e5 Compare May 24, 2023 16:26
@github-actions github-actions bot changed the title chore(main): release 0.5.5 chore(main): release 0.6.0 Jun 1, 2023
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 6f119e5 to ecf860b Compare June 1, 2023 14:22
@mnaser mnaser merged commit 18197fa into main Jun 1, 2023
@mnaser mnaser deleted the release-please--branches--main branch June 1, 2023 16:39
@github-actions
Copy link
Contributor Author

github-actions bot commented Jun 1, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cluster status is not updated properly
1 participant