Adds latest-allowed-stable option

[vahid-haghighat]

Description

In the current implementation, the latest and latest-allowed options have potentially confusing behaviours:

• latest-allowed can unexpectedly include pre-release versions
• latest is limited to stable versions only

This discrepancy can cause issues, particularly in CI/CD pipelines where version predictability is crucial.

To address this, I propose adding a new latest-allowed-stable option that:

• Ensures only stable versions are considered
• Preserves existing behaviour for current users
• Provides a clear, predictable way to select the most recent stable version

This change gives developers more granular control over version selection while maintaining backward compatibility.

[grillba]

cant it just fix it so latest-allowed works in the same way as latest? This was fixed in version 1.0.0 for latest

Note I'm not a maintainer on this repo, just chanced upon this same issue

Edit: tenv supports only installing stable releases: tenv terraform install latest-allowed

[kvendingoldo]

@grillba you can use latest-pre

[vahid-haghighat]

cant it just fix it so latest-allowed works in the same way as latest? This was fixed in version 1.0.0 for latest

Note I'm not a maintainer on this repo, just chanced upon this same issue

Edit: tenv supports only installing stable releases: tenv terraform install latest-allowed

It is possible to fix the latest-allowed, but I wasn't sure if that was the right move. Maybe some people are using pre-releases with latest-allowed? I would have no idea why, though 😄