Skip to content

fix: Use new patch handler for AWS and Docker ClusterClasses #1050

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

Merged
merged 2 commits into from
Feb 13, 2025

Conversation

jimmidyson
Copy link
Member

@jimmidyson jimmidyson commented Feb 13, 2025

This means no automatic rollout of clusters using the existing
ClusterClasses and will not break any downstream project tests
that might be checking for that.

Same approach as previously done for Nutanix ClusterClass -
should have done this at the same time.

This means no automatic rollout of clusters using the existing
ClusterClasses and will not break any downstream project tests
that might be checking for that.
@github-actions github-actions bot added fix and removed fix labels Feb 13, 2025
@jimmidyson jimmidyson merged commit 52779a5 into main Feb 13, 2025
21 checks passed
@jimmidyson jimmidyson deleted the jimmi/v2-handlers-aws-docker branch February 13, 2025 13:40
jimmidyson added a commit that referenced this pull request Feb 13, 2025
🤖 I have created a release *beep* *boop*
---


## 0.27.1 (2025-02-13)

<!-- Release notes generated using configuration in .github/release.yaml
at main -->

## What's Changed
### Fixes 🔧
* fix: Use new patch handler for AWS and Docker ClusterClasses by
@jimmidyson in
#1050
### Other Changes
* build: Updated goreleaser kos.repositories config by @jimmidyson in
#1051


**Full Changelog**:
v0.27.0...v0.27.1

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants