Oscar

I've noticed that commits are often cherry-picked to multiple release branches. I suspect this just keeps it simpler for them when doing so.

@theOehrly No problem! I can do it. However using the feedback you provided in the code review I realize that this function maybe isn't needed. All I needed was `result...

Thank you @theOehrly for your help and support.

I just want to say thank you for working on this @seanschneeweiss and reviewers! We are **really** looking forward to this feature.

Beautiful work @UmiVilbig! I would love to see it.

@UmiVilbig I think this is a good description: https://github.com/firstcontributions/first-contributions You can't cause any damage to the project. So don't worry about breaking anything.

We were also surprised by this. I would like to suggest a few possible solutions: * Could maybe the Sidero provider check for `TALOS_VERSION` and use it if set? *...

@smira Do you think any of the suggestions above are acceptable? I can write a warning in the docs, but if it's possible to "solve" then I think it's preferable.

From our perspective it was a surprise because we thought we had set an explicit version. If I recall correctly we booted a mgmt machine with Talos `1.5.5`, we used...

PR has now been rebased with main, changes added to a `Cluster API v1.3 compared to v1.4` doc and fixed the documentation about the new clusterctl upgrade syntax .