feat: support latest as a version and use it as the default input

[purpleclay]

closes #114

[purpleclay]

This change has the added benefit of not needing to keep this repository in sync with each dagger release.

[jedevc]

cc @gerhard

One thing I do like about the current setup is that if you pin this repo to a specific version/tag then it forces a specific dagger version - instead of needing to track multiple versions.

That said, I've seen latest as a pattern as well, specifically with the docker build actions - so maybe this is also viable.

[gerhard]

Thanks for contributing this @purpleclay!

The problem with defaulting to latest is that we could break pipelines out of the blue. 0.8.0 had several breaking changes, 0.9.0 had a few & both 0.10.0 & 0.11.0 changed fundamental aspects in how the CLI & the Engine work together.

I am all for adding latest as an explicit version value. Would that work @purpleclay?

[purpleclay]

Thanks for contributing this @purpleclay!

The problem with defaulting to latest is that we could break pipelines out of the blue. 0.8.0 had several breaking changes, 0.9.0 had a few & both 0.10.0 & 0.11.0 changed fundamental aspects in how the CLI & the Engine work together.

I am all for adding latest as an explicit version value. Would that work @purpleclay?

@gerhard happy to make that change 👍

[purpleclay]

@gerhard I have made those changes now

[gerhard]

Looking at this now.

[gerhard]

👍 🚀

[gerhard]

Thank you @purpleclay 💪

This change is now available in the updated v5 as well as the new v5.3.0