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

Bump versions #192

Merged
merged 2 commits into from
Aug 15, 2024
Merged

Bump versions #192

merged 2 commits into from
Aug 15, 2024

Conversation

jacobweinstock
Copy link
Member

Description

Bump versions across CAPT and the Stack playgrounds.

Why is this needed

Fixes: #

How Has This Been Tested?

Manually tested all playgrounds.

How are existing users impacted? What migration steps/scripts do we need?

Checklist:

I have:

  • updated the documentation and/or roadmap (if required)
  • added unit or e2e tests
  • provided instructions on how to upgrade

This gets the CAPT playground using Kubernetes
1.29 with the OS image coming from the official
tinkerbell/cluster-api-provider-tinkerbell repo.

Signed-off-by: Jacob Weinstock <[email protected]>
This gets the K3D cluster to 1.30, uses the
latest Helm chart, and local binaries like kubectl
and helm.

Signed-off-by: Jacob Weinstock <[email protected]>
@jacobweinstock jacobweinstock merged commit 0420ec1 into tinkerbell:main Aug 15, 2024
3 checks passed
@jacobweinstock jacobweinstock deleted the bump-versions branch August 15, 2024 21:29
ttwd80 pushed a commit to ttwd80/tinkerbell-playground that referenced this pull request Sep 7, 2024
Bump versions:

## Description

<!--- Please describe what this PR is going to change -->
Bump versions across CAPT and the Stack playgrounds.

## Why is this needed

<!--- Link to issue you have raised -->

Fixes: #

## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
Manually tested all playgrounds.


## How are existing users impacted? What migration steps/scripts do we need?

<!--- Fixes a bug, unblocks installation, removes a component of the stack etc -->
<!--- Requires a DB migration script, etc. -->


## Checklist:

I have:

- [ ] updated the documentation and/or roadmap (if required)
- [ ] added unit or e2e tests
- [ ] provided instructions on how to upgrade
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.

1 participant