Major version floating tag (v1) not pointing to latest release - inconsistent tagging strategy

[micbegin]

The current tagging strategy is problematic as it doesn't follow the common pattern observed in most popular GitHub Actions repositories. Major version floating tags (like v1) should always point to the latest stable release within that major version. However, in this repository, the v1 tag points to an older commit (adf3041) rather than the latest v1.1.0 release (29ea35c).

This inconsistency creates confusion and potential issues for users. For example, PR #28 fixed a critical dry run behavior issue that prevented checking if a function existed. Since many users use the floating v1 tag (very common with GitHub Actions), they would miss this important fix that's available in v1.1.0 and continue experiencing the dry run failure issue.

In the context of Semantic Versioning (SemVer), a 'floating tag' refers to a version alias that automatically updates to point to the latest available release within a specified range. For instance, v1 should always point to v1.latest_minor.latest_patch. While SemVer defines strict rules for incrementing version numbers, floating tags extend this by providing convenience for consumers.

For reference, the actions/checkout repository demonstrates proper tagging strategy where major version floating tags (v1, v2, v3, v4) always point to the latest release within their respective major versions, ensuring users automatically receive critical fixes without having to manually track and update to specific minor versions.

If floating tags are available for this action, they should follow this rule or be removed entirely to avoid confusion.