fix limactl run bug by treating unparseable versions as latest instead of crashing during template validation.

[olamilekan000]

change fixes limactl run bug  by treating unparseable versions as latest instead of crashing
during template validation.

fixes issue

[olamilekan000]

can someone review this? thanks @afbjorklund @jandubois

[jandubois]

Thanks, LGTM

However, some comment changes and an additional test should be added.

Also might be a good idea to update all the GitHub actions that do a checkout with check-depth: 0 (see #3495 (comment)). That should not be necessary after this change, otherwise there is something wrong with it.

[jandubois]

Please resolve merge conflicts by rebasing on latest master

[jandubois]

Thanks, LGTM

I see we have a bunch of checkout actions that explicitly specify fetch-depth: 1, which is redundant because it is the default. I wonder if those were added to explicitly show that we don't need the tags? I feel like they could all be removed, but should probably be done in a separate PR.

[jandubois]

Looks like the colima test is now failing: https://github.com/lima-vm/lima/actions/runs/17002343354/job/48209754473?pr=3820

 + colima start
  time="2025-08-16T03:19:41Z" level=fatal msg="lima compatibility error: invalid semver version for Lima: d65ae91 is not in dotted-tri format"

[olamilekan000]

Looks like the colima test is now failing: https://github.com/lima-vm/lima/actions/runs/17002343354/job/48209754473?pr=3820

 + colima start
  time="2025-08-16T03:19:41Z" level=fatal msg="lima compatibility error: invalid semver version for Lima: d65ae91 is not in dotted-tri format"

I think it might be because it is because of this.

        ref: ${{ github.event.pull_request.head.sha }}

Let me remove it and see what happens.

[olamilekan000]

Thanks, LGTM

I see we have a bunch of checkout actions that explicitly specify fetch-depth: 1, which is redundant because it is the default. I wonder if those were added to explicitly show that we don't need the tags? I feel like they could all be removed, but should probably be done in a separate PR.

Yes, I had the same thought too but I didn't want to touch them since the linked issue explicitly mentioned just fetch-depth: 0

[jandubois]

I think it might be because it is because of this.

No, it is not. It is a check in colima itself that fails. It will only work with a limactl with a proper version: https://github.com/abiosoft/colima/blob/da28a8334746baa56361c05d4c0c2c1e1b2966b3/cmd/start.go#L88-L89

So for the colima test step we need to build with fetch-depth: 0. Add a comment to the step explaining why this is still required.